[JBoss JIRA] (JBWS-4083) testcases using wsprovide and wsconsume failure with new -secmgr flag
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-4083?page=com.atlassian.jira.plugin.... ]
R Searls updated JBWS-4083:
---------------------------
Description:
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.
was:
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.
> 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
>
> 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)
6 years, 5 months
[JBoss JIRA] (JBWS-4083) testcases using wsprovide and wsconsume failure with new -secmgr flag
by R Searls (JIRA)
R Searls created JBWS-4083:
------------------------------
Summary: 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
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)
6 years, 5 months
[JBoss JIRA] (JBWS-4082) Upgrade to Apache CXF 3.2.1
by Alessio Soldano (JIRA)
Alessio Soldano created JBWS-4082:
-------------------------------------
Summary: Upgrade to Apache CXF 3.2.1
Key: JBWS-4082
URL: https://issues.jboss.org/browse/JBWS-4082
Project: JBoss Web Services
Issue Type: Feature Request
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-5.2.0.Final
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBWS-4075) jaxws-tools-maven-plugin doesn't work on JDK9
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-4075?page=com.atlassian.jira.plugin.... ]
R Searls commented on JBWS-4075:
--------------------------------
I have not been able to reproduce the error documented but there were issues with the project tests. I've updated the archive versions. This cleaned up the test failures. I
hope it will resolve your issue as well.
Please rebuild this code with jdk 8
https://github.com/rsearls/jaxws-tools-maven-plugin/tree/JBWS-4075-workin...
and test the plugin in your jdk9 env.
> jaxws-tools-maven-plugin doesn't work on JDK9
> ---------------------------------------------
>
> Key: JBWS-4075
> URL: https://issues.jboss.org/browse/JBWS-4075
> Project: JBoss Web Services
> Issue Type: Task
> Components: jaxws-tools-maven-plugin
> Affects Versions: jbossws-jaxws-tools-maven-plugin-1.2.0.Beta1
> Reporter: Tomaz Cerar
> Assignee: R Searls
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> When running on JDK9 plugin fails with CNFE classes from jaxb impl
> Maybe fix would be as simple as using jaxb-ri 2.3 dependency explicitly.
> {noformat}
> Caused by: java.lang.NoClassDefFoundError: com/sun/istack/FinalArrayList
> at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:246)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:137)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:108)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:412)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:375)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:279)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.init(PluginLoader.java:78)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.<init>(PluginLoader.java:73)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.newInstance(PluginLoader.java:106)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.<init>(WSDLToJava.java:48)
> at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:308)
> at org.jboss.ws.api.tools.WSContractConsumer.consume(WSContractConsumer.java:225)
> ... 29 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBWS-4075) jaxws-tools-maven-plugin doesn't work on JDK9
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-4075?page=com.atlassian.jira.plugin.... ]
R Searls updated JBWS-4075:
---------------------------
Assignee: R Searls
> jaxws-tools-maven-plugin doesn't work on JDK9
> ---------------------------------------------
>
> Key: JBWS-4075
> URL: https://issues.jboss.org/browse/JBWS-4075
> Project: JBoss Web Services
> Issue Type: Task
> Components: jaxws-tools-maven-plugin
> Affects Versions: jbossws-jaxws-tools-maven-plugin-1.2.0.Beta1
> Reporter: Tomaz Cerar
> Assignee: R Searls
> Fix For: jbossws-cxf-5.2.0.Final
>
>
> When running on JDK9 plugin fails with CNFE classes from jaxb impl
> Maybe fix would be as simple as using jaxb-ri 2.3 dependency explicitly.
> {noformat}
> Caused by: java.lang.NoClassDefFoundError: com/sun/istack/FinalArrayList
> at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:246)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:137)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:108)
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:286)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:412)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:375)
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:279)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.init(PluginLoader.java:78)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.<init>(PluginLoader.java:73)
> at org.apache.cxf.tools.wsdlto.core.PluginLoader.newInstance(PluginLoader.java:106)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.<init>(WSDLToJava.java:48)
> at org.jboss.wsf.stack.cxf.tools.CXFConsumerImpl.consume(CXFConsumerImpl.java:308)
> at org.jboss.ws.api.tools.WSContractConsumer.consume(WSContractConsumer.java:225)
> ... 29 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBWS-4048) Elytron integration
by Stanislav Grushevskiy (JIRA)
[ https://issues.jboss.org/browse/JBWS-4048?page=com.atlassian.jira.plugin.... ]
Stanislav Grushevskiy edited comment on JBWS-4048 at 11/1/17 5:56 AM:
----------------------------------------------------------------------
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
Undertow and EJB security works fine, security domain is visible to them.
was (Author: stanislav1125):
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
Undertow and EJB security works fine, security domain is visible for them.
> Elytron integration
> -------------------
>
> Key: JBWS-4048
> URL: https://issues.jboss.org/browse/JBWS-4048
> Project: JBoss Web Services
> Issue Type: Task
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.1.7.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBWS-4048) Elytron integration
by Stanislav Grushevskiy (JIRA)
[ https://issues.jboss.org/browse/JBWS-4048?page=com.atlassian.jira.plugin.... ]
Stanislav Grushevskiy edited comment on JBWS-4048 at 11/1/17 5:22 AM:
----------------------------------------------------------------------
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
Undertow and EJB security works fine, security domain is visible for them/
was (Author: stanislav1125):
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
> Elytron integration
> -------------------
>
> Key: JBWS-4048
> URL: https://issues.jboss.org/browse/JBWS-4048
> Project: JBoss Web Services
> Issue Type: Task
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.1.7.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBWS-4048) Elytron integration
by Stanislav Grushevskiy (JIRA)
[ https://issues.jboss.org/browse/JBWS-4048?page=com.atlassian.jira.plugin.... ]
Stanislav Grushevskiy edited comment on JBWS-4048 at 11/1/17 5:22 AM:
----------------------------------------------------------------------
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
Undertow and EJB security works fine, security domain is visible for them.
was (Author: stanislav1125):
https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF...
WebServices Subsystem
There is adapter in webservices subsystem to make authentication works for elytron security domain automatically. Like configure with legacy security domain, you can configure elytron security domain in deployment descriptor or annotation to secure webservice endpoint.
How should I config WildFly to make authentication works for elytron security domain in webservices?
Error: jboss.ws.endpoint "..." is missing "...-security-domain"
Undertow and EJB security works fine, security domain is visible for them/
> Elytron integration
> -------------------
>
> Key: JBWS-4048
> URL: https://issues.jboss.org/browse/JBWS-4048
> Project: JBoss Web Services
> Issue Type: Task
> Components: jbossws-cxf, jbossws-integration
> Reporter: Alessio Soldano
> Assignee: Alessio Soldano
> Fix For: jbossws-cxf-5.1.7.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months