-
Bug
-
Resolution: Done
-
Major
-
jbossws-cxf-5.2.0.Final
-
None
Running 2 existing test cases in wildlfy-10.0.0+ with security fails do to a bug in
jboss-module. Our 2 test cases uncovered this issue.
tests
- org.jboss.test.ws.jaxws.cxf.jbws3713.ClientBusStrategyTestCase
- org.jboss.test.ws.jaxws.jbws1666.JBWS1666TestCase
Both of these test generate a cmd that uses jboss-module to execuate a client jar.
The generated command looks like this.
/usr/java/jdk1.8.0_72/jre/bin/java \
-Djavax.xml.ws.spi.Provider=org.jboss.wsf.stack.cxf.client.ProviderImpl \
-Dlog4j.output.dir=/home/rsearls/j1/jbws/jbossws-cxf/modules/testsuite/cxf-tests/target \
-Dorg.jboss.ws.cxf.jaxws-client.bus.strategy=NEW_BUS \
-Djava.security.policy=/home/rsearls/j1/jbws/jbossws-cxf/modules/testsuite/cxf-tests/target/test-resources/jaxws/cxf/jbws3713/WEB-INF/jbws3713-client-security.policy \
-jar /home/rsearls/j1/wfly10/wildfly/build/target/wildfly-10.0.0.Final/jboss-modules.jar \
-mp /home/rsearls/j1/wfly10/wildfly/build/target/wildfly-10.0.0.Final/modules \
-secmgr \
-jar /home/rsearls/j1/jbws/jbossws-cxf/modules/testsuite/cxf-tests/target/test-libs/jaxws-cxf-jbws3713-client.jar \
http://127.0.0.1:8080/jaxws-cxf-jbws3713//HelloService?wsdl 4 5
In addition to the fix in jboss-module our code needs 2 changes. One a security.policy
file must be passed on the cmd-line. Two the -secmgr flag must be provided just after the
jboss-module.jar declaration.
A bug has been filed against jboss-module and linked here.
- is caused by
-
MODULES-307 Running JARs directly results in the JAR getting no secmgr permissions
- Resolved