Bugs item #1021980, was opened at 2004-09-03 11:05
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1021980&group_id=22866
Category: JBossServer
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Scott M Stark (starksm)
Assigned to: Scott M Stark (starksm)
Summary: Need better control of JNDI call by value
Initial Comment:
The default optimization call by reference of JNDI
lookups conflicts with applications using scoping of
classes when they try to share values between
themselves using JNDI. There are currently two workarounds:
1. Include the shared classes in some shared deployment
or class loader. The easiest way to do this is by
putting the shared class into a jar in the
server/xxx/lib directory.
2. Force the jndi lookup from the war to go over rmi
which causes the values to be copied from the class
loading space of the sar into the war. To do this the
war code simply passes in a Context.PROVIDER_URL:
Properties env = new Properties();
env.setProperty(Context.PROVIDER_URL,
"localhost:1099");
InitialContext ctx = new InitialContext(env);
With the addition of the call-by-value ejb setting and
isolated ear deployer setting, there should be more
control over the jndi naming service as well.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1021980&group_id=22866
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
