jboss-modules LinkageError / Translet class loaded, but unable to create translet instance.

[stephen.flynn]

I am attempting to upgrade from Wildfly 8.0.0.Final to 8.1.0.Final and have encountered the following exception when creating an instance of javax.xml.transform.Transformer from an instance of javax.xml.transform.Templates.

The stack trace is as follows...

Caused by: javax.xml.transform.TransformerConfigurationException: Translet class loaded, but unable to create translet instance.

at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.defineTransletClasses(TemplatesImpl.java:369) [rt.jar:1.7.0_45]

at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.getTransletInstance(TemplatesImpl.java:383) [rt.jar:1.7.0_45]

at com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl.newTransformer(TemplatesImpl.java:418) [rt.jar:1.7.0_45]

This is a trapped Linkage error. The stack trace doesn't help much as the root cause of this seems to be that the redirected TransformerFactory produced by jboss-modules (of type __redirected.__TransformerFactory) behaves differently between 8.0.0 (containing jboss-module 1.3.1) and 8.1.0 (containing jboss-module 1.3.3).

When calling TransformerFactory.newTemplates() from  __redirected.__TransformerFactory class in jboss-module 1.3.1 the factory produces an instance of type org.apache.xalan.xsltc.trax.TemplatesImpl.

When calling TransformerFactory.newTemplates() from  __redirected.__TransformerFactory class in jboss-module 1.3.3 the factory produces an instance of type com.sun.org.apache.xalan.internal.xsltc.trax.TemplatesImpl. This appears to be wrong (or at the very least a significant change in behaviour) and leads to a Linkage error when the Templates instance is subsequently used to produce a Transfomer.

[dmarcou]

Has there been any movement on this issue, I am also experiencing the exact same issue, when upgrading from Jboss 7.1.1.Final to Wildfly 8.1.0Final ?

[dmlloyd]

I'm not sure why this would suddenly start happening.  Can you test in upstream to see if the problem exists there?  What about 8.2.0.Final?

[dmarcou]

Not sure what you mean by upstream, however I did just install the 8.2.0.Final update and I see the same exception there.

[dmarcou]

So I solved my problem by including xalan and xerces jars in my web application. Previously I had been trying to reference them via the jboss modules.

[skay088]

Hi,

I'm encountering same issue with WildFly 8.1-FInal

However, with the same WAR artifact deployed on

1)  Jboss 7.1 -> No LinkageError

2) upgrading to WildFly 8.2-final -> same issue / LinkageError

=> This bug hasn't been corrected (!!!).

I think you'll share my opinion : It is absolutely not safe and Xalan /Jaxp management is clearly the job of the AS / not the application !!

DId you find something else than your work-around / embeeding Xalan ?

BR

[dmlloyd]

No, the problem has not been solved yet.  I can tell you that the problem seems extremely unlikely to have been introduced between JBoss Modules 1.3.1 and 1.3.3; it may be a result of some change to the application server's class loader building, but I'm not sure about that either.

[skay088]

Thanks for your reply; meanwhile I opened an issue :

https://issues.jboss.org/browse/WFLY-4174

Tell me if this is the correct process !

A workaround consist in embeeding Xalan / see my comments.

But could you tell me if it is possible to add/expose the Wildfly's Xalan distrib into the classpath directly through standalone.xml configuration or something smarter, like adding an extra module.xml configuration ?

BR

[foutjo]

I am getting the same issue with wildfly 9.0.

I was previously running 7.1 and worked without giving exception.

Can anyone tell me if this issue has been fixed yet?

Or is there some type of work around that I can apply?

Any help is greatly appreciated.