JAXP, Saxon 6.2 and Orion

[Ted R. Rice]

        I am using Saxon 6.2, from a JSP Tag Extension and am
experiencing the following situation. I have a compiled code base runs
fine with versions 1.3.8 and 1.4.5. However, when I move to 1.4.7 I
experience the following runtime exceptions.

        java.lang.NoSuchMethodError:
javax.xml.transform.TransformerConfigurationException: method
<init>(Ljava/lang/Exception;)V not found
         at /index.jsp._jspService(/index.jsp.java:105)
         at com.orionserver.http.OrionHttpJspPage.service(JAX)
         at com.evermind.server.http.HttpApplication.xu(JAX)
         at com.evermind.server.http.JSPServlet.service(JAX)
         at com.evermind.server.http.d4.s3(JAX)
         at com.evermind.server.http.d4.s1(JAX)
         at com.evermind.server.http.eg.s9(JAX)
         at com.evermind.server.http.eg.dr(JAX)
         at com.evermind.util.f.run(JAX)
        

        OR

        java.lang.NoSuchMethodError
        at
com.icl.saxon.TransformerFactoryImpl.getAssociatedStylesheet(Transformer
FactoryImpl.java:219)
        at
com.apama.apps.util.TransformManager.buildCompositeStyleSheet(TransformM
anager.java:147)
        at
com.apama.apps.jsp.taglibs.xsl.ApplyXSLTag.getTransformManager(ApplyXSLT
ag.java:263)
        at
com.apama.apps.jsp.taglibs.xsl.ApplyXSLTag.processXML(ApplyXSLTag.java:1
94)
        at
com.apama.apps.jsp.taglibs.xsl.ApplyXSLTag.processContent(ApplyXSLTag.ja
va:175)
        at
com.apama.apps.jsp.taglibs.xsl.ApplyXSLTag.doEndTag(ApplyXSLTag.java:135
)
        at /index.jsp._jspService(/index.jsp.java:100)
        at com.orionserver.http.OrionHttpJspPage.service(JAX)
        at com.evermind.server.http.HttpApplication.xu(JAX)
        at com.evermind.server.http.JSPServlet.service(JAX)
        at com.evermind.server.http.d4.s3(JAX)
        at com.evermind.server.http.d4.s1(JAX)
        at com.evermind.server.http.eg.s9(JAX)
        at com.evermind.server.http.eg.dr(JAX)
        at com.evermind.util.f.run(JAX)

        The first exception is being thrown when the code is debugged
attatching to Orion, the second is when being run without an attatched
debug process.

        I am curious if anyone has experience issues with Orion's
version of JAXP and the one used by Saxon. 

        I understand the details here are very vague, but I am not
having much luck tracking down specifics in this particular situation. 

        Thanks,

         

        Ted Rice

winmail.dat