The last time I tried to "minimize" Axis2 was last summer, during the 1.1-SNAPSHOT days, so the following may no longer be accurate, but: in my experience, there are too many casual dependencies between the JARs in Axis2 to make any significant reductions. Muse uses the most basic functionality of Axis2 (doc-literal, Axiom-style service methods), but still we found that most of the JARs were required because of one or two .class dependencies throughout the modules.
The Axis2 team may have cleaned this up prior to the 1.1 release - there were a lot of changes in the summer/fall - but I haven't gone back and checked. The best place to ask would be axis-user - they can probably tell you what JARs you can remove for basic functionality. Or you can try to remove one JAR at a time (like we did) and see what breaks. Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 02/19/2007 05:26:46 PM: > So far for Muse 2.1.0, I've been using the mini-servlet deployment to > Tomcat so far, and it works fine for me. Now, I need to upgrade to the > Axis2 packaging. There are a lot of Axis2 jars that come with the Muse > download, and the samples deploy all of the jars. > > Does anyone know the minimum set of Axis2 jars required to get Muse to > run in Tomcat? For now, I just need Axis2 for extracting custom > properties from the SOAP request header. I also see that there is an > xbean-2.2.0.jar included with Axis2, which I will not need because I'm > already deploying with a separate XmlBeans 2.2.0 package. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
