This is well answered in the following thread in the dev list. An issue caused due to cross posting..
~Thilina
On 11/24/05, Ajith Ranabahu <[EMAIL PROTECTED]
> wrote:
hi all,
Well I'm not sure why nobody seems to answer (probably the guys were pretty busy :() but the answer is actually pretty simple. include a lib folder into the archive and put all the jars that you need in there.
The service has a seperate classloader so none of the jars you put in the service lib folder will show up in the other applications--
On 11/24/05, Routis Babis <[EMAIL PROTECTED] > wrote:Tony Dean wrote:
> Forwarding to axis-user listserve.
>
> -----Original Message-----
> From: Tony Dean [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 22, 2005 8:16 AM
> To: axis-dev@ws.apache.org
> Subject: [Axis2] Deployment packaging
>
> What is the Axis2 best practice for packaging a complex web service application that spans multiple jars? Essentially, to create an Axis2 web service endpoint, you must create a single jar with the following contents:
> meta-inf/services.xml
> meta-inf/services.wsdl
> MyWebServicePortTypeSkeleton.class
>
> My concern is making other dependent jars available on the classpath and doing so without affecting other applications.
>
> Thanks.
>
> Tony Dean
> SAS Institute Inc.
> 919.531.6704
> [EMAIL PROTECTED]
>
> SAS... The Power to Know
> http://www.sas.com
>
>
It is strange that although many people keep asking the same question
(including myself), no one in this list has given an answer
Ajith Ranabahu
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/ http://www.bloglines.com/blog/Thilina
