> That's a good idea, thanks for the info. Not as good as yours:
adding the ejb-jar to the classpath in jboss' startup script also seems to break jboss' auto-deploy feature :-( > I solved the problem differently - I added my jar to JBOSS_HOME/dist/lib/ext. But >it accomplishes the same thing - it > gets the jar into Tomcat's classpath. this works for me also. > So, I am up and running but I don't think either of these solutions is ideal. I >don't like junking up startup scripts or > lib/ext with application-specific stuff. When I deploy a web application, I can add >jars to the application's classpath > by putting them WEB-INF/lib or adding to the manifest. Is there no way to do >something similar in the soap deployment > descriptor when deploying a soap service? AFAIK no, but i am pretty new to soap. > It requires you to specify the name of the java class that implements the > service but doesn't seem to provide any way for you to tell it where to find that >class. > This sounds like a deficiency to me... interesting. Bernd
