Chad, It's a bit fluid...Example if you are running in JDK1.4 you don't need xml-apis-1.0.b2.jar and xalan-2.7.0.jar. If you are running in JDK1.6, you don't need stax-api-1.0.1.jar. If you don't need our experimental wsdl20 support, then you can drop woden-1.0.0M6.jar. If you don't run xpath over axiom, then you can drop jaxen-1.1-beta-10.jar. I think the stax parser in JDK1.6 may work in most cases, then you won't need wstx-asl-3.2.0.jar. So in the end, you have to do this yourself, for your use case, for your environment what whatever you do. make sure you do three things...test, test, test :)
thanks, dims On 2/7/07, ChadDavis <[EMAIL PROTECTED]> wrote:
> Here's what i use: I think you can strip it down further. > > XmlSchema-1.2.jar > activation-1.1.jar > annogen-0.1.0.jar > axiom-api-1.2.2.jar > axiom-impl-1.2.2.jar > axis2-adb-1.1.1.jar > axis2-adb-codegen-1.1.1.jar > axis2-codegen-1.1.1.jar > axis2-java2wsdl-1.1.1.jar > axis2-kernel-1.1.1.jar > axis2-tools-1.1.1.jar > backport-util-concurrent-2.2.jar > commons-codec-1.3.jar > commons-httpclient-3.0.1.jar > commons-logging-1.1.jar > jaxen-1.1-beta-10.jar > mail-1.4.jar > neethi-2.0.jar > stax-api-1.0.1.jar > woden-1.0.0M6.jar > wsdl4j-1.6.2.jar > wstx-asl-3.2.0.jar > xalan-2.7.0.jar > xbean-2.2.0.jar > xml-apis-1.0.b2.jar > Thanks. Ideally, I'd like to know exactly. But that's just me being picky. Still, I hate to introduce resources into my project that I don't know exactly their use. Its probably no big deal, but to my simple mind, a pile of jar files poses unknown organizational threats. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
