[GLASSFISH-11529] [spec request] The global jndi namespace should not contain local session beans if interapplication calls are not supported. Created: 06/Feb/10  Updated: 29/Sep/10

Status: Open
Project: glassfish
Component/s: ejb_container
Affects Version/s: V3
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: chasetec Assignee: marina vatkina
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issuezilla Id: 11,529

 Description   

This is kind of a follow up to a bug where I was asking for default JNDI names
before EJB 3.1 (https://glassfish.dev.java.net/issues/show_bug.cgi?id=577).

I love the new default JNDI names and I think the different namespaces
(global,app,module) where a great idea however I have one complaint.

The specs don't require support for inter-application calls on local session
beans. Even though some app servers allow it I'm fine with GlassFish not
allowing it. However I think it unnecessary and confusing to publish global JNDI
names for local session beans that can't be called.

I'd like to see the spec and GlassFish only require the creation of global JNDI
names for EJBs that support inter-application calling.



 Comments   
Comment by chasetec [ 06/Feb/10 ]

To clarify "I'd like to see the spec and GlassFish only require the creation of
global JNDI names for EJBs that support inter-application calling."

I mean just the global namespace. There should still be standard jndi names for
local session beans in the app and module namespaces.

Comment by marina vatkina [ 29/Sep/10 ]

The current spec says this: "The container registers a separate JNDI name entry
for each local business interface, each remote business interface, and any
no-interface view, 2.x local home interface, and 2.x remote home interface."

Generated at Tue Feb 09 21:44:13 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.