August 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3773: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1077262|https://bugzilla.redhat.com/show_bug.cgi?id=1077262] from VERIFIED to CLOSED > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3750 at 8/7/14 8:05 AM: --------------------------------------------------------------- Integration of code for jbws-cxf.5.0.0. The following repos with commits. https://source.jboss.org/changelog/JBossWS?cs=18822 (spi) https://source.jboss.org/changelog/JBossWS?cs=18823 (common) https://source.jboss.org/changelog/JBossWS?cs=18824 (800 ASIL) https://github.com/asoldano/wildfly/pull/9 (pull request) was (Author: rsearls): Integration of code for jbws-cxf.5.0.0. The following repos with commits. https://svn.jboss.org/repos/jbossws/spi/trunk ( Committed revision 18822 ) https://svn.jboss.org/repos/jbossws/common/trunk ( Committed revision 18823 ) https://svn.jboss.org/repos/jbossws/container/wildfly80/branches/jbossws-... ( Committed revision 18824. ) https://github.com/asoldano/wildfly/pull/9 (pull request) > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > Attachments: feature-doc-fragment.txt > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3802) Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3802?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3802: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1111046|https://bugzilla.redhat.com/show_bug.cgi?id=1111046] from ASSIGNED to NEW > Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile > -------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3802 > URL: https://issues.jboss.org/browse/JBWS-3802 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue, to JBoss WS. > When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault. > This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3750: --------------------------------------- Thanks Rebecca for the documentation additions. I've reverted the change to the WFLY8 section as we won't have another WFLY 8.x version including JBossWS 5 series (the changes to the integration layer does not count here, the doc there is meant for vanilla WFLY 8 version) > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > Attachments: feature-doc-fragment.txt > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3750 at 8/7/14 6:33 AM: --------------------------------------------------------------- Integration of code for jbws-cxf.5.0.0. The following repos with commits. https://svn.jboss.org/repos/jbossws/spi/trunk ( Committed revision 18822 ) https://svn.jboss.org/repos/jbossws/common/trunk ( Committed revision 18823 ) https://svn.jboss.org/repos/jbossws/container/wildfly80/branches/jbossws-... ( Committed revision 18824. ) https://github.com/asoldano/wildfly/pull/9 (pull request) was (Author: rsearls): Integration of code for cxf.5.0.0. The following repos with commits. https://svn.jboss.org/repos/jbossws/spi/trunk ( Committed revision 18822 ) https://svn.jboss.org/repos/jbossws/common/trunk ( Committed revision 18823 ) https://svn.jboss.org/repos/jbossws/container/wildfly80/branches/jbossws-... ( Committed revision 18824. ) https://github.com/asoldano/wildfly/pull/9 (pull request) > Add ability to rewrite path in WSDL URL references > -------------------------------------------------- > > Key: JBWS-3750 > URL: https://issues.jboss.org/browse/JBWS-3750 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Kyle Lape > Assignee: R Searls > Fix For: jbossws-cxf-5.0 > > Attachments: feature-doc-fragment.txt > > > Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3802) Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3802?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3802: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1111046|https://bugzilla.redhat.com/show_bug.cgi?id=1111046] from NEW to ASSIGNED > Empty response returned when SOAP Fault is thrown from an endpoint having WS-Security Policy Signature profile > -------------------------------------------------------------------------------------------------------------- > > Key: JBWS-3802 > URL: https://issues.jboss.org/browse/JBWS-3802 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.4, jbossws-cxf-4.3 > Reporter: Tadayoshi Sato > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > > Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue, to JBoss WS. > When a web service has a WS-Security Signature policy in its WSDL and throws a SOAP Fault, it returns an empty HTTP response that has zero-length of content to client instead of the SOAP Fault. > This happens only with Signature policy and doesn't happen with any other WS-Security policies like UsernameToken, or without WS-Security. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3777) CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3777: ----------------------------------------------- Pavel Slavicek <pslavice(a)redhat.com> changed the Status of [bug 1080321|https://bugzilla.redhat.com/show_bug.cgi?id=1080321] from VERIFIED to CLOSED > CXF-5645: wsp:Optional isn't adhered to for WS-RM policy in WSDL > ---------------------------------------------------------------- > > Key: JBWS-3777 > URL: https://issues.jboss.org/browse/JBWS-3777 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Environment: Red Hat JBoss EAP 6.2.0 > Reporter: Tadayoshi Sato > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0 > > Attachments: ws-rm.zip > > > Please port the fix for [CXF-5645|https://issues.apache.org/jira/browse/CXF-5645] to JBoss WS CXF. > Here is the original issue description: > The {{wsp:Optional}} attribute doesn't work for WS-RM in JBoss WS CXF. As far as the specs tell both WS-Addressing 1.0 and WS-RM 1.1 should support {{wsp:Optional}}, that is, if {{wsp:Optional}} is set to {{true}} on a WS-RM policy the WS-RM policy should become optional -- the endpoint should allow both messages with and without WS-RM \[1\]. However, my experimentation showed that it actually doesn't. > What I did is as follows (see the attached reproducer for details): > # Configured in WSDL ({{greeting.wsdl}}) an endpoint as optionally WS-RM enabled like the following: > {code:xml} > <wsdl:binding name="GreetingServiceSoapBinding" type="tns:GreetingService"> > <wsp:Policy xmlns:wsp="http://www.w3.org/2006/07/ws-policy"> > <wsam:Addressing xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > wsp:Optional="true" /> > <wsrmp:RMAssertion xmlns:wsrmp="http://schemas.xmlsoap.org/ws/2005/02/rm/policy" > wsp:Optional="true" /> > </wsp:Policy> > ... > {code} > # Sent a WS-RM unaware (= no SOAP header) SOAP request from the client but got the following SOAP Fault: > {code:xml} > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Body> > <soap:Fault> > <faultcode>soap:Server</faultcode> > <faultstring>WS-Addressing is required by this endpoint.</faultstring> > </soap:Fault> > </soap:Body> > </soap:Envelope> > {code} > [1] In WS-RM Policy 1.1 p.8: > {quote} > /wsrmp:RMAssertion/@wsp:Optional="true" > Per WS-Policy, this is compact notation for two policy alternatives, one with and one without the assertion. The intuition is that the behavior indicated by the assertion is optional, or in this case, that WS-ReliableMessaging MAY be used. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 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 August 2014