[jbossws-issues] [JBoss JIRA] (JBWS-4083) testcases using wsprovide and wsconsume failure with new -secmgr flag

[R Searls (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

R Searls updated JBWS-4083:
---------------------------
    Assignee: R Searls


> testcases using wsprovide and wsconsume failure with new -secmgr flag
> ---------------------------------------------------------------------
>
>                 Key: JBWS-4083
>                 URL: https://issues.jboss.org/browse/JBWS-4083
>             Project: JBoss Web Services
>          Issue Type: Bug
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-5.2.0.Final
>            Reporter: R Searls
>            Assignee: R Searls
>
> There are 3 tests that use ${WILDFLY_HOME}/bin/wsprovide.sh
> * org.jboss.test.ws.jaxws.jbws2528.JBWS2528TestCase
> * org.jboss.test.ws.jaxws.jbws2529.JBWS2529TestCase
> * org.jboss.test.ws.jaxws.smoke.tools.WSProvideScriptTestCase
> and 1 test that uses  ${WILDFLY_HOME}/bin/wsconsume.sh
> * org.jboss.test.ws.jaxws.smoke.tools.WSConsumeScriptTestCase
> When running with wildfly in *secmgr* mode  and testing with the *-secmgr *flag the tests fail.
> This is because utilities wsprovide and wsconsume in wildfly are broken.  They are not handling the (new) -secmgr flag properly.   Changes to jboss-module.jar requires this flag.
> Jiras have been filed in wildfly and linked here.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)