I't probably on the Web Service binding, including: * Start an embedded Jetty * Load the axis2 configuration (I observe that we do that for each service with binding.ws) * Generate the WSDL from java * Publish the web service
Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On May 18, 2010, at 3:04 PM, Jean-Sebastien Delfino wrote: > The samples/launcher-embedded-jse test case contains the following two test > methods: > > public class LauncherTestCase { > > @Test > public void testCOntributionBindingSCACalculator() throws Exception { > SampleJSELauncher.main(new String[] > {"contribution-binding-sca-calculator"}); > } > > @Test > public void testCOntributionBindingWSCalculator() throws Exception { > SampleJSELauncher.main(new String[] > {"contribution-binding-ws-calculator"}); > } > } > > These two test methods just bootstrap the Tuscany runtime and invoke a simple > business method on a Java component. > > On my laptop, testContributionBindingSCACalculator takes 1.5 sec, but > testContributionBindingWSCalculator() takes 19.5 sec. > > Are others seeing that too? Any idea where the 18 sec are spent? Is that time > just spent bootstrapping the Web Service binding? > > -- > Jean-Sebastien
