I'm going out on a limb here, but I think the problem is that you have two
different instances of javax.jms.InitialContextFactory.
Usually the problem with class loading is that you are missing a class. But,
the problem here is that com.swiftmq.jndi.InitialContextFactoryImpl is not
the type that we expect it should be. Not having the source in front of me,
I imagine that NamingManager is looking for something of the type
InitialContext. Clearly, swift's class implements this interface. The only
time I've ever seen a type check like this fail is if the calling code has a
different class loader than the swift class. In which case there are two
instances of javax.naming.InitialContextFactory, one in each classloader and
they are not equal. It may also be possible to have the problem if the
classes are from two different jars in the system path (I haven't tested
it).
I would double check that you do not have two jndi.jar's in the classpath.
Make sure that there are no extra copies of the javax.jms classes (be sure
to check in smqclient.jar which I don't have in front of me). Keep in mind
that Tomcat likes to make modifications to the classpath in the bat files
and that it has its own classloader (well, at least one) in addition to the
system loader.
I'm only using Tomcat 3.1, so I can't give any more details on where to
look, but I think that's where your problem is.
Good luck.
-rick
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
