Hi,
it is strongly recomended to avoid using j2ee.jar with jboss. If ever, make
sure it is BEHIND ejb.jar from JBoss on your classpath!
I would recomend using JBossMQ the JBoss JMS provider, even if you are
changing to a different app-server, it can be used freely!
(And it is far more robust and faster than suns implementation)
Burtkhard
----- Original Message -----
From: "David M. Lang" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 6:05 PM
Subject: [JBoss-user] JBoss and J2SDKEE1.3
> Hi,
>
> I have a session bean that uses a delegate class (a standard Java class)
to
> write a message to a JMS topic using the javax.jms package from Sun's
> J2SDKEE1.3 (Beta 2). The delegate class works fine stand-alone. I then
add
> it to the bean, and run up JBoss (version 2.2.2). It complains that it
> can't find the javax.jms.JMSException class (or any JMS class I suspect).
> Adding J2SDKEE1.3 to the class path gives the following warning when
JBoss
> is started up :-
>
> Please make sure the following is intended (check your classpath):
> jndi.properties is read from jar:file:/e:/jdk/j2sdkee1.3/j2ee.jar.
>
> This subsequently causes various NamingExceptions and
IllegalStateExceptions
> when JBoss componets are loaded up. I'm not sure what I'm doing wrong.
Any
> thoughts greatly appreciated.
>
> Regards,
>
>
> David Lang
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
