jbossws-issues July 2013

jbossws-issues@lists.jboss.org

1 participants
95 discussions

[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: ----------------------------------------------- vramik(a)redhat.com made a comment on [bug 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] Verified in ER02. I've left <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host> unchanged and it's working as expected. > 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

10 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: ----------------------------------------------- vramik(a)redhat.com changed the Status of [bug 905410|https://bugzilla.redhat.com/show_bug.cgi?id=905410] from ON_QA to VERIFIED > 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> changed the Status of [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] from NEW to MODIFIED > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3601) SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3601?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3601: ----------------------------------------------- Carlo de Wolf <cdewolf(a)redhat.com> made a comment on [bug 913411|https://bugzilla.redhat.com/show_bug.cgi?id=913411] ER3 contains 2.6.8 which has supposedly fixed the issue. > SOAPFaultException cannot render SOAP 1.2 Fault Subcode in CXF > -------------------------------------------------------------- > > Key: JBWS-3601 > URL: https://issues.jboss.org/browse/JBWS-3601 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBoss Enterprise Application Platform 6 > Reporter: Tadayoshi Sato > Assignee: Alessio Soldano > Labels: cxf > Fix For: jbossws-cxf-4.2 > > > Backport https://issues.apache.org/jira/browse/CXF-4790, which is the root cause. The code below doesn't render {{<soapenv:Subcode>}}. > {code} > import javax.xml.soap.SOAPConstants; > import javax.xml.soap.SOAPFactory; > import javax.xml.soap.SOAPFault; > import javax.xml.ws.soap.SOAPFaultException; > ... > SOAPFactory factory = SOAPFactory.newInstance(SOAPConstants.SOAP_1_2_PROTOCOL); > SOAPFault fault = factory.createFault("Operator not found", new QName(SOAPConstants.URI_NS_SOAP_1_2_ENVELOPE, "Receiver")); > fault.appendFaultSubcode(new QName("...", "OperatorNotFound")); > ... > throw new SOAPFaultException(fault); > {code} -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3658) JBOSS 7.0.13 SPRING 1.5 : org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

by fabien.tribouillois＠accenture.com tribouillois (JIRA)

fabien.tribouillois(a)accenture.com tribouillois created JBWS-3658: -------------------------------------------------------------------- Summary: JBOSS 7.0.13 SPRING 1.5 : org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. Key: JBWS-3658 URL: https://issues.jboss.org/browse/JBWS-3658 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: test Reporter: fabien.tribouillois(a)accenture.com tribouillois Hello, We have migrated from JBOSS4 to JBOSS7. The applciation run, there is only some web services are failing with the following error : org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces. If replcace the jboss7 xalan lib by xalan library 2.7.0 from xalan, that run well. But i think, it's not the best way to fixe my issue. Then I try to embaded the lib in the applciation war and i added a jboss-deployment.xml in to exclude the org.apache/xalan lib from jboss, but that does not work. please can you help me ? -- 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

10 years, 10 months

1
0
0 / 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues July 2013