2008/3/5 Matthew Peters <[EMAIL PROTECTED]>: > In case this helps, I have found that the precise set of jars needed (on > 1.0.1) to run the calculator sample under WebSphere (and I suppose Tomcat > would be the same) is: > > activation-1.1.jar > axiom-api-1.2.5.jar > axiom-impl-1.2.5.jar > cglib-nodep-2.1_3.jar > commons-logging-1.1.jar > geronimo-commonj_1.1_spec-1.0.jar > jaxen-1.1-beta-9.jar > mail-1.4.jar > neethi-2.0.2.jar > stax-api-1.0-2.jar > tuscany-assembly-1.0.1-incubating.jar > tuscany-assembly-xml-1.0.1-incubating.jar > tuscany-assembly-xsd-1.0.1-incubating.jar > tuscany-binding-sca-1.0.1-incubating.jar > tuscany-binding-sca-xml-1.0.1-incubating.jar > tuscany-contribution-1.0.1-incubating.jar > tuscany-contribution-impl-1.0.1-incubating.jar > tuscany-contribution-java-1.0.1-incubating.jar > tuscany-contribution-namespace-1.0.1-incubating.jar > tuscany-core-1.0.1-incubating.jar > tuscany-core-databinding-1.0.1-incubating.jar > tuscany-core-spi-1.0.1-incubating.jar > tuscany-databinding-1.0.1-incubating.jar > tuscany-definitions-1.0.1-incubating.jar > tuscany-definitions-xml-1.0.1-incubating.jar > tuscany-domain-1.0.1-incubating.jar > tuscany-domain-api-1.0.1-incubating.jar > tuscany-host-embedded-1.0.1-incubating.jar > tuscany-implementation-java-1.0.1-incubating.jar > tuscany-implementation-java-runtime-1.0.1-incubating.jar > tuscany-implementation-java-xml-1.0.1-incubating.jar > tuscany-interface-1.0.1-incubating.jar > tuscany-interface-java-1.0.1-incubating.jar > tuscany-interface-java-xml-1.0.1-incubating.jar > tuscany-node-1.0.1-incubating.jar > tuscany-node-api-1.0.1-incubating.jar > tuscany-policy-1.0.1-incubating.jar > tuscany-policy-logging-1.0.1-incubating.jar > tuscany-policy-xml-1.0.1-incubating.jar > tuscany-sca-api-1.0.1-incubating.jar > wsdl4j-1.6.2.jar > wstx-asl-3.2.1.jar > xalan-2.7.0.jar > xercesImpl-2.8.1.jar > xml-apis-1.3.03.jar > > > Matthew Peters >
>From looking at this before I think axiom and its dependencies are being brought in through the Tuscany policy modules, would it possible to refactor the policy code so that they're not needed here or is there something inherent in policy that requires axiom? ..ant
