[
https://issues.jboss.org/browse/WFLY-4317?page=com.atlassian.jira.plugin....
]
xiaodong xie commented on WFLY-4317:
------------------------------------
Well, thanks a lot for so prompt reply, David. :-)
Actually, I have no idea about the existence of the "sun.jdk" module before.
Thanks for hinting me. :)
We just fixed this class loading issue by the mentioned workaround when migrating from
Glassfish 3 to Wildfly 8.x.
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)