Michael O'Brien [
http://community.jboss.org/people/mfobrien] replied to the
discussion
"EJB3 jndi lookup failed on JBOSS EAP only due to ProxyFactory not bound"
To view the discussion, visit:
http://community.jboss.org/message/533316#533316
--------------------------------------------------------------
Issue resolved,
Use a 3-part (app_name/bean_name/remote) or
(app_name/remote-bean_name/qualified_bean_name) EJB JNDI lookup instead of a 2 part
(without the app_name prefix)
The JBoss EAP server registers the following name
2010-03-22
11:07:33,326 INFO [org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase]
(HDScanner) Binding the following Entries in Global JNDI:
TestRunner - EJB3.x Default Remote Business Interface
eclipselink-advanced-field-access-model/TestRunner/remote-org.eclipse.persistence.testing.framework.server.TestRunner
- EJB3.x Remote Business Interface
2010-03-22 11:07:39,797 INFO [STDOUT] (WorkerThread#0[127.0.0.1:62483]) [EL Info]:
2010-03-22 11:07:39.797--ServerSession(4488512)--EclipseLink, version: Eclipse Persistence
Services - 2.1.0.qualifier
Use the name
"eclipselink-advanced-field-access-model/TestRunner/remote-org.eclipse.persistence.testing.framework.server.TestRunner"
in the JNDI context lookup to get an EJB @Remote @Stateless session bean $Proxy.
Note: the name can also be
"eclipselink-advanced-field-access-model/TestRunner/remote" if @Remote on the
remote interface and @Stateless defaults are used without overrides.
see
http://wiki.eclipse.org/EclipseLink/Bugs/305331thank
http://wiki.eclipse.org/EclipseLink/Bugs/305331
http://wiki.eclipse.org/EclipseLink/Bugs/305331thank
thank you
/michael
http://www.eclipselink.org http://www.eclipselink.org
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/533316#533316]
Start a new discussion in JNDI and Naming at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]