April 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3627) JBoss AS -> WildFly scripts migration

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3627: ------------------------------------- Summary: JBoss AS -> WildFly scripts migration Key: JBWS-3627 URL: https://issues.jboss.org/browse/JBWS-3627 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3626) Ability to globally configure SSL settings for JAX-WS clients

by Kyle Lape (JIRA)

Kyle Lape created JBWS-3626: ------------------------------- Summary: Ability to globally configure SSL settings for JAX-WS clients Key: JBWS-3626 URL: https://issues.jboss.org/browse/JBWS-3626 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Kyle Lape Right now, every JAX-WS client that needs to connect to an SSL-enabled endpoint needs to utilize the {{TLSClientParameters}} object from the CXF API library to configure SSL/TLS (unless everything is already configured in the JDK for this particular endpoint). It would be nice if this could be configured globally (perhaps in standalone.xml/domain.xml?) and without CXF-specific APIs needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3625) Fix the WS-I BSP test failures

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3625?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3625: ---------------------------------- Component/s: jbossws-cxf > Fix the WS-I BSP test failures > -------------------------------- > > Key: JBWS-3625 > URL: https://issues.jboss.org/browse/JBWS-3625 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.1.2 > Reporter: Jim Ma > Fix For: jbossws-cxf-4.2 > > Attachments: jbossws-bsp-log-report.zip > > > There are several failures when run the ws-i bsp tests with the following tests: > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.*TestCase > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase. > The failure of org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase is caused by the GCM is not the allowed by WS-I BSP profile. We can simply remove this tests or change the tests to use the standard EncryptionMethod. > The failures of org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase are assertion failures : "A wsse:Reference element does NOT contain a ValueType attribute". Look at if this is the issue in wss4j. > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3622) Restore HTTPS tests w/ Undertow

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3622?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3622: ---------------------------------- Component/s: jbossws-cxf jbossws-integration > Restore HTTPS tests w/ Undertow > ------------------------------- > > Key: JBWS-3622 > URL: https://issues.jboss.org/browse/JBWS-3622 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > The tests requiring https connector are currently failing for multiple reasons as a consequence of AS8 having moved to Undertow; those currently include: > *) different dmr invocation required in RemoteDeployer to setup the https listener/connector > *) misc bugs in Undertow -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3620) Authentication failures w/ Undertow

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3620?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3620: ---------------------------------- Component/s: jbossws-integration > Authentication failures w/ Undertow > ----------------------------------- > > Key: JBWS-3620 > URL: https://issues.jboss.org/browse/JBWS-3620 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of AS8 having moved to use Undertow, we have some failures on authentication. Need to investigate further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3620) Authentication failures w/ Undertow

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3620?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3620: ---------------------------------- Component/s: jbossws-cxf > Authentication failures w/ Undertow > ----------------------------------- > > Key: JBWS-3620 > URL: https://issues.jboss.org/browse/JBWS-3620 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.2 > > > As a consequence of AS8 having moved to use Undertow, we have some failures on authentication. Need to investigate further. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3569) WSDL produced for a multi-port service contains invalid port addresses in clustered configuration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3569?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3569: ----------------------------------------------- theute(a)redhat.com changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from VERIFIED to CLOSED > WSDL produced for a multi-port service contains invalid port addresses in clustered configuration > ------------------------------------------------------------------------------------------------- > > Key: JBWS-3569 > URL: https://issues.jboss.org/browse/JBWS-3569 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Chris Laprun > Assignee: Alessio Soldano > Priority: Critical > Fix For: jbossws-cxf-4.1.1 > > > Using a loadbalancer fronted cluster and the loadbalancer URL for the WSDL results in ports containing the node URLs instead of the loadbalancer's. > I've tried using the dynamic WSDL rewriting as described in https://docs.jboss.org/author/display/AS71/Advanced+User+Guide but this results in invalid URLs for the ports (with {{jbossws.undefined.host}} as the host name *and* the cluster node port) that haven't been used to access the WSDL, the port used to access the WSDL has the proper address though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3624) Create the test suite to check the wsi-bsp 11 compliance

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3624?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3624: ---------------------------------- Summary: Create the test suite to check the wsi-bsp 11 compliance (was: Create the test suite to check the wsi-bsp 11 complaince) > Create the test suite to check the wsi-bsp 11 compliance > -------------------------------------------------------- > > Key: JBWS-3624 > URL: https://issues.jboss.org/browse/JBWS-3624 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: productization > Reporter: Jim Ma > Assignee: Jim Ma > > Prepare the test suite to check the ws-i bsp compliance for jbossws-cxf/AS release -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3625) Fix the WS-I BSP test failures

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3625?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3625: ------------------------- Attachment: jbossws-bsp-log-report.zip > Fix the WS-I BSP test failures > -------------------------------- > > Key: JBWS-3625 > URL: https://issues.jboss.org/browse/JBWS-3625 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: jbossws-cxf-4.1.2 > Reporter: Jim Ma > Fix For: jbossws-cxf-4.2 > > Attachments: jbossws-bsp-log-report.zip > > > There are several failures when run the ws-i bsp tests with the following tests: > org.jboss.test.ws.jaxws.samples.wsse.policy.basic.*TestCase > org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase. > The failure of org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase is caused by the GCM is not the allowed by WS-I BSP profile. We can simply remove this tests or change the tests to use the standard EncryptionMethod. > The failures of org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase are assertion failures : "A wsse:Reference element does NOT contain a ValueType attribute". Look at if this is the issue in wss4j. > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3625) Fix the WS-I BSP test failures

by Jim Ma (JIRA)

Jim Ma created JBWS-3625: ---------------------------- Summary: Fix the WS-I BSP test failures Key: JBWS-3625 URL: https://issues.jboss.org/browse/JBWS-3625 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jbossws-cxf-4.1.2 Reporter: Jim Ma Fix For: jbossws-cxf-4.2 There are several failures when run the ws-i bsp tests with the following tests: org.jboss.test.ws.jaxws.samples.wsse.policy.basic.*TestCase org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase. The failure of org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase is caused by the GCM is not the allowed by WS-I BSP profile. We can simply remove this tests or change the tests to use the standard EncryptionMethod. The failures of org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.*TestCase are assertion failures : "A wsse:Reference element does NOT contain a ValueType attribute". Look at if this is the issue in wss4j. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2013