"dimitris(a)jboss.org" wrote : Where in the ejb3 deployer code are the jndi
binding created?
|
| I can see an ejb3 ejb being deployed, but the jndi link uses the short name of the
bean (which is wrong) and not the full name:
|
|
| | +- appclient_dep_compat14_50_client (class: org.jnp.interfaces.NamingContext)
| | | +- ejb (class: org.jnp.interfaces.NamingContext)
| | | | +- TestBean[link -> TestBean] (class: javax.naming.LinkRef)
| |
| | +- appclient_deploy_compat14_50_TestBeanHome
| | (proxy: $Proxy58 implements interface
| | com.sun.ts.tests.appclient.deploy.compat14_50.TestBeanHome)
| | +- appclient_deploy_compat14_50_TestBean
| | (proxy: $Proxy56 implements interface
| | com.sun.ts.tests.appclient.deploy.compat14_50.TestBean,interface
| | org.jboss.ejb3.JBossProxy,interface javax.ejb.EJBObject)
| |
These client encs don't look valid either. On the client side the lookup for the
appclient_dep_compat14_50_client/env context is failing. This should have been setup by
the org.jboss.deployment.ClientDeployer.setupEnvironment. The ClientDeployer is in need of
refactoring to separate the parsing, and the org.jboss.ejb3.client.ClientContainer looks
to be doing parsing of descriptors it should not be. The ApplicationClientDD data should
be coming from the server.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083496#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...