Thanks Simon - I'll throw together an example of this behaviour now.

Cheers,

Dave.

--
Dave Sowerby MEng MBCS



On Sat, Aug 2, 2008 at 11:41 AM, Simon Laws <[EMAIL PROTECTED]> wrote:
>
>
> On Sat, Aug 2, 2008 at 10:59 AM, Dave Sowerby <[EMAIL PROTECTED]>
> wrote:
>>
>> Hi All,
>>
>> I'm having an issue with 1.3 RC3 when trying to lookup a Service from
>> with an EJB (within Websphere 6.1)
>>
>> After quite a bit of investigation, I managed to dig out this stack,
>> which had been consumed:
>>
>> Caused by:
>> org.apache.tuscany.sca.contribution.service.ContributionReadException:
>> org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte
>> 2 of 2-byte UTF-8 sequence.
>>        at
>> org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.read(CompositeDocumentProcessor.java:107)
>>        at
>> org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.read(CompositeDocumentProcessor.java:56)
>>        at
>> org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.read(ExtensibleURLArtifactProcessor.java:96)
>>        at
>> org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:492)
>>        at
>> org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:387)
>>        at
>> org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:189)
>>        at
>> org.apache.tuscany.sca.node.impl.NodeImpl.configureNode(NodeImpl.java:489)
>>        at
>> org.apache.tuscany.sca.node.impl.NodeImpl.<init>(NodeImpl.java:186)
>>        at
>> org.apache.tuscany.sca.node.impl.NodeFactoryImpl.createSCANodeFromClassLoader(NodeFactoryImpl.java:37)
>>
>> Further debugging highlighted that the contribution is loaded from a
>> wsjar:file:/ protocol based file, is it possible that a change similar
>> to TUSCANY-2219 is required here as well to cope with this case?
>>
>> I can prepare an example which demonstrates this case if it's useful.
>>
>> Cheers,
>>
>> Dave.
>>
>> --
>> Dave Sowerby MEng MBCS
>
> Hi Dave
>
> It looks like TUSCANY-2219 has been applied to NodeImpl but of course the
> code path in your example may not be hitting it for some reason. Looking at
> the stack trace it looks like it has actually identified a .composite file
> artifact in the contribution as it's got into the read phase but then if
> gets the Xerces exception. Is there anything strange about your composite
> file.
>
> If you attach an example one of us can give it a spin and see what's going
> on.
>
> Thanks
>
> Simon
>

Reply via email to