snip...
> org.apache.tuscany.sca.interfacedef.wsdl.impl.InvalidWSDLException:
> Element cannot be resolved: {http://sample/}sayHello
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl$WSDLPart.<init>(WSDLOperationIntrospectorImpl.
> java:276)
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getMessageType(WSDLOperationIntrospectorImpl.j
> ava:194)
> at
> org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl.getInputType(WSDLOperationIntrospectorImpl.jav
Ok, so I guess I was just lucky. The particular error could be caused
by any number of things, e.g. the XML/XSD implementation varies
slightly or even some other difference is causing imports/includes to
be processed differently. My preference would be to do the refactoring
to get rid of the intermediate file and to process includes/imports
properly and see if the result still exhibits this JVM/Maven
dependency error.
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
