I don't know
exactly your situation, please check the
deployed a EJB 3.0 application in an xxx-ejb.jar
configured an openejb-jar.xml deployment plan where you set an artifactId for
your app, let's say "MyApp"
have a session bean you want connect to, let's say
have build a remote interface for your session bean (EJB 3.0 means a simple
interface), let's say "MySessionRemote"
then the following is the right jndi name to get a
connection to your bean
You have to use the fully qualified class name for
I tried to define a jndi name for the session bean
inside the deployment plan, but this doesn't work (deployment is ok but lookup
I'm making some progress while moving my app to
I have some questions about JNDI.
first I've noticed that
when connecting to remote EJB (for tests I use 127.0.0.1:4201)
I don't have
to provide principals and credentials, when I provide system/manager I get
"AuthenticationException: This principal is not authorized"
successfully connect to 4201 port I need to comment out java.naming.security
Properties p = new
I can connect
Context c = new InitialContext(p);
quick question: how
to turn security back?
i'm using EJB 2.x (G1.1) and I'm trying to connect
to EJB through the "remote" JNDI but I get:
javax.naming.NameNotFoundException: /ejb/ModuleFactory does not exist in the
system. Check that the app was successfully
yes, my EAR app is successfully deployed in G2.0, no
errors were reported during deployment...
it all worked on
maybe it's because I didn't provide any principals and
Win a BlackBerry device from O2 with Yahoo!. Enter