You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@santuario.apache.org by "Giedrius Noreikis (Created) (JIRA)" <ji...@apache.org> on 2012/02/07 16:40:59 UTC
[jira] [Created] (SANTUARIO-298) Xalan is still a required
dependency
Xalan is still a required dependency
------------------------------------
Key: SANTUARIO-298
URL: https://issues.apache.org/jira/browse/SANTUARIO-298
Project: Santuario
Issue Type: Bug
Components: Java
Affects Versions: Java 1.5
Reporter: Giedrius Noreikis
Assignee: Colm O hEigeartaigh
It is stated in the release notes that "Xalan is no longer a required dependency". However, running signature creation without it produces an exception:
java.lang.NoClassDefFoundError: org/apache/xml/utils/PrefixResolver
at org.apache.xml.security.transforms.implementations.TransformXPath.enginePerformTransform(TransformXPath.java:105)
at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:304)
at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:281)
at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:272)
at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:248)
<...>
Both TransformXPath and TransformXPath2Filter use the same code:
XPathAPI xpathAPIInstance = new XalanXPathAPI();
if (!XalanXPathAPI.isInstalled()) {
xpathAPIInstance = new JDKXPathAPI();
}
which is supposed to provide a way to get either Xalan or JDK -based XPathAPI implementation.
However, the XalanXPathAPI class in turn imports Xalan classes and hence just can not be loaded without it.
And BTW, I think it would be better to provide a factory to get the XPathAPI implementation from, instead of repeating the above code lines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SANTUARIO-298) Xalan is still a required
dependency
Posted by "Colm O hEigeartaigh (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANTUARIO-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh closed SANTUARIO-298.
-----------------------------------------
> Xalan is still a required dependency
> ------------------------------------
>
> Key: SANTUARIO-298
> URL: https://issues.apache.org/jira/browse/SANTUARIO-298
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.5
> Reporter: Giedrius Noreikis
> Assignee: Colm O hEigeartaigh
> Fix For: Java 1.5.1
>
>
> It is stated in the release notes that "Xalan is no longer a required dependency". However, running signature creation without it produces an exception:
> java.lang.NoClassDefFoundError: org/apache/xml/utils/PrefixResolver
> at org.apache.xml.security.transforms.implementations.TransformXPath.enginePerformTransform(TransformXPath.java:105)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:304)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:281)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:272)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:248)
> <...>
> Both TransformXPath and TransformXPath2Filter use the same code:
> XPathAPI xpathAPIInstance = new XalanXPathAPI();
> if (!XalanXPathAPI.isInstalled()) {
> xpathAPIInstance = new JDKXPathAPI();
> }
> which is supposed to provide a way to get either Xalan or JDK -based XPathAPI implementation.
> However, the XalanXPathAPI class in turn imports Xalan classes and hence just can not be loaded without it.
> And BTW, I think it would be better to provide a factory to get the XPathAPI implementation from, instead of repeating the above code lines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SANTUARIO-298) Xalan is still a required
dependency
Posted by "Colm O hEigeartaigh (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANTUARIO-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated SANTUARIO-298:
------------------------------------------
Fix Version/s: Java 1.5.1
> Xalan is still a required dependency
> ------------------------------------
>
> Key: SANTUARIO-298
> URL: https://issues.apache.org/jira/browse/SANTUARIO-298
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.5
> Reporter: Giedrius Noreikis
> Assignee: Colm O hEigeartaigh
> Fix For: Java 1.5.1
>
>
> It is stated in the release notes that "Xalan is no longer a required dependency". However, running signature creation without it produces an exception:
> java.lang.NoClassDefFoundError: org/apache/xml/utils/PrefixResolver
> at org.apache.xml.security.transforms.implementations.TransformXPath.enginePerformTransform(TransformXPath.java:105)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:304)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:281)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:272)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:248)
> <...>
> Both TransformXPath and TransformXPath2Filter use the same code:
> XPathAPI xpathAPIInstance = new XalanXPathAPI();
> if (!XalanXPathAPI.isInstalled()) {
> xpathAPIInstance = new JDKXPathAPI();
> }
> which is supposed to provide a way to get either Xalan or JDK -based XPathAPI implementation.
> However, the XalanXPathAPI class in turn imports Xalan classes and hence just can not be loaded without it.
> And BTW, I think it would be better to provide a factory to get the XPathAPI implementation from, instead of repeating the above code lines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SANTUARIO-298) Xalan is still a required
dependency
Posted by "Colm O hEigeartaigh (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SANTUARIO-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved SANTUARIO-298.
-------------------------------------------
Resolution: Fixed
> Xalan is still a required dependency
> ------------------------------------
>
> Key: SANTUARIO-298
> URL: https://issues.apache.org/jira/browse/SANTUARIO-298
> Project: Santuario
> Issue Type: Bug
> Components: Java
> Affects Versions: Java 1.5
> Reporter: Giedrius Noreikis
> Assignee: Colm O hEigeartaigh
> Fix For: Java 1.5.1
>
>
> It is stated in the release notes that "Xalan is no longer a required dependency". However, running signature creation without it produces an exception:
> java.lang.NoClassDefFoundError: org/apache/xml/utils/PrefixResolver
> at org.apache.xml.security.transforms.implementations.TransformXPath.enginePerformTransform(TransformXPath.java:105)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:304)
> at org.apache.xml.security.transforms.Transform.performTransform(Transform.java:281)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:272)
> at org.apache.xml.security.transforms.Transforms.performTransforms(Transforms.java:248)
> <...>
> Both TransformXPath and TransformXPath2Filter use the same code:
> XPathAPI xpathAPIInstance = new XalanXPathAPI();
> if (!XalanXPathAPI.isInstalled()) {
> xpathAPIInstance = new JDKXPathAPI();
> }
> which is supposed to provide a way to get either Xalan or JDK -based XPathAPI implementation.
> However, the XalanXPathAPI class in turn imports Xalan classes and hence just can not be loaded without it.
> And BTW, I think it would be better to provide a factory to get the XPathAPI implementation from, instead of repeating the above code lines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira