Hello folks,
I have a few EJBs and I am trying to deploy it on a JBoss2.2 with embedded
tomcat3.2.1.
My deployment goes fine. But my JNDI name bindings are not getting place. It
always puts one of my OLD bean JNDI on the Namespace. And also all my beans
are getting that beans Namespace,which
Sent: jeudi, 31. mai 2001 10:27
To: [EMAIL PROTECTED]
Subject: [JBoss-user] JNDI name bindings are not working properly on
deployment
Hello folks,
I have a few EJBs and I am trying to deploy it on a JBoss2.2 with embedded
tomcat3.2.1.
My deployment goes fine. But my JNDI name bindings
Show your ejb-jar.xml and jboss.xml deployment descriptors.
- Original Message -
From: Selvarajah Vahees [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, May 31, 2001 1:27 AM
Subject: [JBoss-user] JNDI name bindings are not working properly on deployment
Hello folks,
I
Title: RE: [JBoss-user] JNDI name bindings are not working properly on deployment
You are talking about the OLD bean jndi. If you mean you've deployed a jar and all the jndi bindings were correct, then you changed something and restarted, but the changes don't seem to have effect...
Take
Title: RE: [JBoss-user] JNDI name bindings are not working properly on deployment
OK.fine that means if I am to make available my
bean classes to my JSPs in embedded Tomcat, I have to make another jar file
without DDs and put then in the classpath..right?
ok..lemme try
that
vahees
Hello folks,
I have a few EJBs and I am trying to deploy it on a JBoss2.2 with embedded
tomcat3.2.1.
My deployment goes fine. But my JNDI name bindings are not getting place. It
always puts one of my OLD bean JNDI on the Namespace. And also all my beans
are getting that beans Namespace,which I