This content has been marked as final.
Show 4 replies
-
1. Re: Examples
bill.burke Feb 2, 2006 7:17 PM (in response to nholbrook)You'll have to isolate JNDI
look in server/xxx/conf/jboss-service.xml
look for NamingService
set attribute CallByValue to true.
Then you'll have to scope your WARs as defined in our main doco. I have a testcase for this in CVS so I know this works. BTW, you have to communicate through REmote interfaces if you want scoped classloading. -
2. Re: Examples
bill.burke Feb 2, 2006 7:18 PM (in response to nholbrook)FYI, the testcase in cvs is:
ejb3/src/test/org/jboss/ejb3/test/regression/scopedclassloader
build-test.xml creates the jars. -
3. Re: Examples
nholbrook Feb 2, 2006 9:05 PM (in response to nholbrook)Thanks for the help. I'll start playing around.
-
4. Re: Examples
ejb3workshop Feb 3, 2006 7:06 AM (in response to nholbrook)Have a look at the classpath. You should avoid using the classed / jars from JBOSS_HOME/client.
Because you patched 4.0.3SP1, the client jars in the jboss-4.0.3SP1/client directory will be invalid. Build your client classpath from:
1. jboss-4.0.3SP1/lib
2. jboss-4.0.3SP1/server/all/lib
3. jboss-4.0.3SP1/server/all/deploy/ejb3.deployer
4. jboss-4.0.3SP1/server/all/deploy/jboss-aop-jdk50.deployer