Hello Jason,<div>Thanks for your explanation. As I understand it means that correct=expected behaviour of server is to pick managed xalan-j version of translet. </div><div><br></div><div>I didn't investigated what inside of xalan is causing the problem with output malformed XML. I only find out why the output is correct in Jboss 6 EAP and incorrect in Jboss 6, 7 and current head revision. </div>
<div><br></div><div>I even came to point where I can reproduce that problem entirely outside the server (in executable JAR) please find <a href="https://github.com/jjromannet/AS7-6390-reproduction-JAR" target="_blank">https://github.com/jjromannet/AS7-6390-reproduction-JAR</a> </div>
<div>(correct output version on branch for reference)</div><div>In above example TransletFactory is created explicitly but class is same as instantiated by FactoryFinder.</div><div><br></div><div>If TransformerFactoryImpl is taken from org.apache.xalan.processor it produces correct output.</div>
<div><br></div><div>So ... In order to fix this issue - presumably some fix for xalan-j is needed.</div><div><br></div><div>Regards</div><div>Jan Roman</div><div><br><br><div class="gmail_quote">On 20 February 2013 15:48, Jason Greene <span dir="ltr"><<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
On Feb 20, 2013, at 9:47 AM, Jason Greene <<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>> wrote:<br>
<br>
> Replying inline to be more clear.<br>
><br>
> On Feb 20, 2013, at 8:24 AM, Jan J. Roman <<a href="mailto:mail@jjroman.net" target="_blank">mail@jjroman.net</a>> wrote:<br>
><br>
>> Hello everyone,<br>
>> I can not get heard on irc ;-) and forum discussion in development area seems to be a bit dead.<br>
>> I would like to start contributing and I have been trying to resolve issue reported here: <a href="https://issues.jboss.org/browse/AS7-6390" target="_blank">https://issues.jboss.org/browse/AS7-6390</a><br>
>><br>
>> I came to the point where I figured out that the issue is caused by incorrectly picked TransformerFactory class (it is created as an instance of org.apache.xalan.xsltc.trax.TransformerFactoryImpl instead of com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl).<br>
><br>
> That's not quite right. The com.sun.* class is a JDK class it's not in the xalan library we ship. If something ever picks org.apache.xalan.xsltc.trax.TransformerFactoryImpl, it's going to break when a deployment is involved due to the class loading issues I mentioned in the other email.<br>
<br>
</div>Oops that should read: " If something ever picks [com.sun.]org.apache.xalan.xsltc.trax.TransformerFactoryImpl, it's going to break when a deployment is involved due to the class loading issues I mentioned in the other email.<br>
<div><div>--<br>
Jason T. Greene<br>
JBoss AS Lead / EAP Platform Architect<br>
JBoss, a division of Red Hat<br>
<br>
</div></div></blockquote></div><br></div>