[jboss-jira] [JBoss JIRA] (WFLY-4317) JBoss Module does not add package "org.jcp.xml.dsig.internal" as system package
David Lloyd (JIRA)
issues at jboss.org
Wed Feb 4 18:17:49 EST 2015
[ https://issues.jboss.org/browse/WFLY-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037712#comment-13037712 ]
David Lloyd commented on WFLY-4317:
-----------------------------------
Looking at your code, the problem may simply be that you're loading the provider directly. Isn't this provider installed into the JDK?
If so, the code would be something like this:
{code}
XMLSignatureFactory fac = XMLSignatureFactory.getInstance("DOM", "XMLDSig");
{code}
> JBoss Module does not add package "org.jcp.xml.dsig.internal" as system package
> -------------------------------------------------------------------------------
>
> Key: WFLY-4317
> URL: https://issues.jboss.org/browse/WFLY-4317
> Project: WildFly
> Issue Type: Enhancement
> Components: Class Loading
> Affects Versions: 8.2.0.Final
> Reporter: xiaodong xie
> Assignee: David Lloyd
>
> The package "org.jcp.xml.dsig.internal" was included in both JDK 7 and JDK 8, but it is not added as a system package in jboss-module.
> So, if we do this:
> String providerName = System.getProperty("jsr105Provider", "org.jcp.xml.dsig.internal.dom.XMLDSigRI");
> XMLSignatureFactory fac =
> XMLSignatureFactory.getInstance("DOM", (Provider) Class.forName(providerName).newInstance());
> We cannot find this "org.jcp.xml.dsig.internal.dom.XMLDSigRI" at runtime.
> The current workaround is to hack "standalone.conf" file, added "org.jcp.xml.dsig.internal" package after package "org.jboss.byteman".
> if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then
> JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jcp.xml.dsig.internal"
> fi
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jboss-jira
mailing list