Hi,
I am not sure if the answer below solves the problem. Correct me if I am wrong. I have the same problem, i.e. in my environment, I have a large number of jars which are part of my entire EJB application. These have a home under my EAR project, I am having to copy all my jars, which contain classes that need to be exposed as webservices, under axis/web-inf directory. Is it necessary to maintain this second copy. The answer below is referring to axis jars, and not to application jars. Please clarify. Thanks Sagar -----Original Message----- From: Steve Mactaggart [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 07, 2004 6:57 PM To: [EMAIL PROTECTED] Subject: RE: Deployment Question You can include the axis jar files in your application and add the sections from the axis web.xml file to enable the bindings for the AxisServlet. Then axis will have access to the classes deployed in your webapp. Steve > -----Original Message----- > From: Keith Tingle [mailto:[EMAIL PROTECTED] > Sent: Thursday, 8 July 2004 5:25 AM > To: [EMAIL PROTECTED] > Subject: Deployment Question > > Hi- > > It seems the standard way to install a web service with axis > is to install > my .jars into axis/WEB-INF/lib, and then deploy via the axis > admin servlet > and a custom wsdd file, with ant tasks. > > But.. I have an application where the web service interface > is only a small > part of the total functionality of the application. I have > servlets & JSP > pages that also need to be deployed along with the SOAP interfaces. > > How does one build an installation without having to maintain > two copies of > the .jar files, one in the axis/WEB-INF/lib directory and > another copy in my > application? Is there a clean method for allowing axis to > share jars with my > webapp? > > Thanks in advance for any help :) > > Keith > > ************************************************************** > ************* > Notice: This e-mail message, including any attachments, is > for the sole > use of the intended recipient(s) and may contain confidential and > privileged information. Any unauthorized review, copy, use, > disclosure, > or distribution is prohibited. If you are not the intended recipient, > or not an agent of the intended recipient responsible for > delivering this > message, please contact the sender by reply e-mail and > destroy all copies > of the original message.
