Hey Mr. Penella,
You wouldn't happen to have an estimate when this bug will be fixed? This
has caused the dev department here to have to start debugging our code
"remotely" (JBuilder and JRun still on the same machine) from JBuilder4EE to
be able to test/deploy on JRun 3.1. And that just when I had taught everyone
here how to set up local debugging with JRun 3 from JBuilder...
We compile our stuff against J2EE.jar, but test/debug against JRun. So when
we start JRun from within JBuilder to debug, J2EE.jar is in the project path
and it fails miserably.
I'm the dev environment responsible around here, so I would very much
appreciate a fix for this in the near future!
3.1 is great!
- Tormod
-----Original Message-----
From: Steve Penella [mailto:[EMAIL PROTECTED]]
Sent: 16. august 2001 17:44
To: JRun-Talk
Subject: RE: JRun 3.1 upgrade problems
There's a bug in JRun where if j2ee.jar is in your classpath you'll get this
error. If this is the case with you, try removing it.
-----Original Message-----
From: Vijay Menon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 9:55 PM
To: JRun-Talk
Subject: JRun 3.1 upgrade problems
Hi all
I have an application using jrun3.0 as a servlet engine, talking to weblogic
which is the bean container. I tried upgrading to jrun 3.1 and now, the
application doesn't start with the following error. I was wondering if
anyone had a similar problem.
Thanks in advance
Cheers
Vijay
08/16 11:42:22 info (jrunauth) Loading propfile
08/16 11:42:23 error (jrunauth) java:comp/env namespace is only available
from within a J2EE component [javax.naming.NamingException: java:comp/env
namespace is only available from within a J2EE component]
javax.naming.NamingException: java:comp/env namespace is only available from
within a J2EE component
at
com.sun.enterprise.naming.java.javaURLContext.getComponentContext(javaURLCon
text.java:392)
at
com.sun.enterprise.naming.java.javaURLContext.callBindOrRebind(javaURLContex
t.java:124)
at
com.sun.enterprise.naming.java.javaURLContext.bind(javaURLContext.java:80)
at javax.naming.InitialContext.bind(InitialContext.java:358)
at allaire.jrun.servlet.JRunAuthenticator.init(JRunAuthenticator.java:65)
at allaire.jrun.ServletService.init(ServletService.java:66)
at allaire.jrun.ServletService.init(ServletService.java:31)
at
allaire.jrun.servlet.JRunServletLoader.loadServletInstance(JRunServletLoader
.java:203)
at allaire.jrun.servlet.JRunSE.initService(JRunSE.java:891)
at allaire.jrun.servlet.JRunSE.initServices(JRunSE.java:858)
at allaire.jrun.servlet.JvmContext.initServices(JvmContext.java:130)
at allaire.jrun.servlet.JRunSE.init(JRunSE.java:222)
at allaire.jrun.servlet.JvmContext.init(JvmContext.java:69)
at allaire.jrun.ServletService.init(ServletService.java:66)
at allaire.jrun.ServletService.init(ServletService.java:31)
at JRun.main(JRun.java:172)
08/16 11:42:23 info (JRun) Loading jdbc
08/16 11:42:23 error (jdbc) Can not create JNDI initial context: Cannot
instantiate class: "weblogic.jndi.TengahInitialContextFactory"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
