January 2013 - jbossws-issues - Jboss List Archives

[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 made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Needs WS patch + https://github.com/gatein-prod/gatein-portal/pull/7 Assigning to Honza, make the status to "POST" (Patch submitted, not included) > 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, 10 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 MODIFIED to POST > 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, 10 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 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] from NEW to ASSIGNED > 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, 10 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: ----------------------------------------------- claprun(a)redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Note that applying the change to wsdl-host only seems to work *when* the JBoss WS patch has been applied. It seems that using a non-patched JBoss WS version results in WSRP not working at all in clustered or single-node mode since the port URLs use jbossws.undefined.host instead of localhost in that case and are not being rewritten. > 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, 10 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: ----------------------------------------------- Michal Vanco <mvanco(a)redhat.com> made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Hi, I just verified clustering scenario with <wsdl-host>jbossws.undefined.host</wsdl-host> on producer nodes and it worked perfect. Now it's possible to refresh consumer or directly display remote portlet after failover - these two main scenarios were expected! WSDL was properly rewritten and it included loadbalancer host instead of specific producer node! I also tried <wsdl-host>jbossws.undefined.host</wsdl-host> at standalone.xml for singlenode testing of wsrp and it worked as expeceted -> it seems to be safe to use above wsdl-host as default. This have to be done for CR01 build (who is gonna do it? Honza/Chris?). > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3593) @javax.xml.ws.BindingType or @javax.xml.ws.soap.MTOM have a different behaviour with jbossws-cxf than jbossws-native

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3593?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3593: ---------------------------------- Fix Version/s: jbossws-cxf-4.2 > @javax.xml.ws.BindingType or @javax.xml.ws.soap.MTOM have a different behaviour with jbossws-cxf than jbossws-native > -------------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3593 > URL: https://issues.jboss.org/browse/JBWS-3593 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-native > Affects Versions: jbossws-cxf-4.0.2, jbossws-native-4.0.2 > Environment: Jboss AS 7.1.1Final > Reporter: A l e c C R E S T A N > Fix For: jbossws-cxf-4.2 > > > On JBoss AS 7.1.1, with the following service implementation: > {code} > @WebService(...) > @javax.xml.ws.BindingType (value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_MTOM_BINDING) > public class SEIImpl { > ... > public DataHandler getBin() {...} /* maps to a type="xs:base64Binary" in wsdl */ > public List<String> getString(){...} /* maps to sequence of String in wsdl */ > ... > } > {code} > With the default *jbossws-cxf*, the responses are: > - for getString() method > Content-Type: multipart/related; type="application/xop+xml"; ... > - for getBin() method > Content-Type: multipart/related; type="application/xop+xml"; ... > -> +both responses are MTOM/XOP modified ! The getString() response should not.+ > With *jbossws-native* (after the jbossws stack switching) , the responses are the expected ones: > - for getString() method > Content-Type: text/xml;charset=UTF-8 <env:Envelope .... text content ..../env:Envelope> > - for getBin() method > Content-Type: multipart/related; type="application/xop+xml"; ... > Best regards, > Note: same behaviour with @javax.xml.ws.soap.MTOM or SOAP11HTTP_MTOM_BINDING -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3593) @javax.xml.ws.BindingType or @javax.xml.ws.soap.MTOM have a different behaviour with jbossws-cxf than jbossws-native

by A l e c C R E S T A N (JIRA)

A l e c C R E S T A N created JBWS-3593: ------------------------------------------- Summary: @javax.xml.ws.BindingType or @javax.xml.ws.soap.MTOM have a different behaviour with jbossws-cxf than jbossws-native Key: JBWS-3593 URL: https://issues.jboss.org/browse/JBWS-3593 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-4.0.2, jbossws-cxf-4.0.2 Environment: Jboss AS 7.1.1Final Reporter: A l e c C R E S T A N On JBoss AS 7.1.1, with the following service implementation: {code} @WebService(...) @javax.xml.ws.BindingType (value=javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_MTOM_BINDING) public class SEIImpl { ... public DataHandler getBin() {...} /* maps to a type="xs:base64Binary" in wsdl */ public List<String> getString(){...} /* maps to sequence of String in wsdl */ ... } {code} With the default *jbossws-cxf*, the responses are: - for getString() method Content-Type: multipart/related; type="application/xop+xml"; ... - for getBin() method Content-Type: multipart/related; type="application/xop+xml"; ... -> +both responses are MTOM/XOP modified ! The getString() response should not.+ With *jbossws-native* (after the jbossws stack switching) , the responses are the expected ones: - for getString() method Content-Type: text/xml;charset=UTF-8 <env:Envelope .... text content ..../env:Envelope> - for getBin() method Content-Type: multipart/related; type="application/xop+xml"; ... Best regards, Note: same behaviour with @javax.xml.ws.soap.MTOM or SOAP11HTTP_MTOM_BINDING -- 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, 10 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: ----------------------------------------------- claprun(a)redhat.com changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ASSIGNED to MODIFIED > 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, 10 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: ----------------------------------------------- claprun(a)redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] I think it's safe to use in non-clustered environment as well, yes. However, this should be confirmed by QA. > 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, 10 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 made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Is it safe to put as default, or does it work only with a loadbalancer ? > 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, 10 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 January 2013