Guy Rouillier wrote: > Don't put anything in classpath. It's tempting, and it can make > development easier, and you can probably get along fine for awhile. But > sooner or later, you'll get bizarre problems. The most common is that > updates to your EJBs don't take (i.e, they appear to deploy properly, > but when you invoke methods on a new version, the old version is run.) > For 2.4.x, set JBOSS_CLASSPATH as required. For 3.0, which I haven't > used much, there are additional mechanisms for specifying required > runtime jars.
What's the best way to deploy a SOAP service through JBoss+TomCat without messing with JBoss's classpath? The SOAP documentation tells me that I must put my service's classes in my servlet container's classpath. -- Richard Kasperowski (mailto:[EMAIL PROTECTED]) Tel: 617-576-1552, Fax: 617-576-2441 http://www.altisimo.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
