On Wed, Aug 10, 2011 at 9:51 AM, Simon Laws <simonsl...@googlemail.com> wrote:
> 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.
>
It does still have the same error. I initially coded it without the
intermediate file and only added this clunky file based dummy
contribution approach to try to make the code work as closely as
possible to the Tuscany file based contribution processing to see if
the problem was being caused by my code.
...ant
