[ http://issues.apache.org/jira/browse/XALANJ-2063?page=history ]
Brian Minchau reassigned XALANJ-2063:
-------------------------------------
Assign To: Ramesh Mandava
I'm assigning this issue to Ramesh, although given the testcase this looks like
a user error. Xalan-J has two JAXP implementations. If one used the JAXP APIs
to get a transformer factory and a SAX transformer factory one would have
stayed consistently in one implementation. But explicitly creating objects, one
from one JAXP implementation, and one from the other, and mixing them looks
like a user error.
> ClassCastException in org.apache.xalan.xsltc.trax.TransformerFactoryImpl
> ------------------------------------------------------------------------
>
> Key: XALANJ-2063
> URL: http://issues.apache.org/jira/browse/XALANJ-2063
> Project: XalanJ2
> Type: Bug
> Components: transformation
> Versions: 2.6
> Environment: Windows XP, JDK1.5.0_01
> Reporter: PJ Fanning
> Assignee: Ramesh Mandava
> Attachments: cdcatalog.xsl
>
> Occurs in method newTransformerHandler(Templates templates). There is a cast
> to TransformerImpl. There is more than one class shipped in the xalan jar
> that subclasses javax.xml.transform.Transformer.
> The background to this is that I created the Templates object using a
> different TransformerFactory (also a Xalan factory).
> The factory used to create the templates object was created using:
> javax.xml.transform.TransformerFactory#newInstance()
> The factory used to create the transformer handler object was created using:
> javax.xml.transform.SAXTransformerFactory#newInstance()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
