On jars deployed in Jboss container they all assume the InitialContext
configured in jndi.properties file. However, through every JSP file that
uses my EJBs (Jboss with embedded Tomcat), I need to tell the InitialContext
java.util.Properties prop = new java.util.Properties();
I decided to code a class that has this hardcoded but I still have to call
it in every file and if my app server changes I need to modify this class.
I developed my EJB & JSP with Inprise App Server + Tomcat and I just call
without need to specify the context:
javax.naming.InitialContext rowcontext = new javax.naming.InitialContext();
How can the same be achieved making the deployment generic?
Thanks in advance,
After following the directions on 'How-to package and deploy an EAR file on
(http://www.jboss.org/documentation/HTML/ch11.html#howtotomcat) and a few
other modifications, I finally got my J2EE App deployed and loading
JBoss2.2.2-Tomcat3.2.2. I'm certain my ear archive is put together correctly
as it has worked on other servers. But now when I browse to my application
... I get 404 errors with the following error output.
[Service Control] Started 25 services
[Default] JBoss 2.2.2 Started in 0m:40s
2001-06-30 12:28:15 - Ctx( ): 404 R( + /acais + null) null
I set the context path in my ear archive's application.xml with the
What am I missing?
Get latest updates about Open Source Projects, Conferences and News.