Yes i'm using the ightweight xslt component.
In the future i'll switch to the standard component.
At the moment i'm not switching because i'm using cimero tool that
generate sa using the lw component.
With the patched code that i described it's working.
Andrea Zoppello
Adrian Co ha scritto:
Are you using the lightweight xslt component?
I've seen this problem when using the lightweight xslt component. I
would advise switching to the jbi compliant saxon component for xslt.
Andrea Zoppello wrote:
Hi,
I 've tried to port a simple service assembly like this:
- BC1(HTTP-SOAP) - > SE(XSLTComponent ) -> BC2
to smx 3.1 and i've noticed that it's not working.
After a detailed debug the problem seems to be in transformContent
method, the problem occur
when this instruction
Source src = in.getContent();
return an object of type StaxSource. I've noticed this because when
smx is running with a simple listener
that print out the MessageExchange the sa is working!!! In that case
in the "transformContent" method
the in.getContent() is a DOMSource object.
I've resolved this adding this lines of code and transforming always
the Source in a StringSource object:
SourceTransformer st = new SourceTransformer();
String str = st.toString(src);
src = new StringSource(str);
Andrea Zoppello
!DSPAM:507,461b3bb328611885597236!
