April 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3759) Bug in schemalocation for swaref for Jboss EAP 6.2

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3759?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3759: -------------------------------- Richard, I get the following error page when attempting to download the WAR and ZIP files. The file system for the given user is unavailable, please try again later. If the problem persists please contact Webdrift. Would you either upload those archives as attachments in this jira or email them to me? > Bug in schemalocation for swaref for Jboss EAP 6.2 > -------------------------------------------------- > > Key: JBWS-3759 > URL: https://issues.jboss.org/browse/JBWS-3759 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2.3 > Reporter: Richard Borge > Assignee: R Searls > Priority: Minor > Labels: cxf, eap-6.2 > > I am using Jboss EAP-6.2 for a SOAP service which uses the Datahandler to handle returned streams. In the WSDL, I am expecting the xsd for swaref to be imported, but the schemalocation gets messed up. Instead of "http://ws-i.org/profiles/basic/1.1/swaref.xsd" I get "http://localhost:8080/soaptest/mys?xsd=http://ws-i.org/profiles/basic/1.1...". This is a bit of a problem because, among other things, it messes up soapUI for thos of our customers that want to test the service. > I have tried to look through the jboss code, but it is very hard to find where the localhost-part gets concatenated onto the swaref XSD. > The source code: > http://folk.uio.no/richared/jboss/soaptest.zip -- 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, 3 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3626?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3626: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > 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 > Fix For: jbossws-cxf-5.0 > > > 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

10 years, 3 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 updated JBWS-3750: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > 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 > Fix For: jbossws-cxf-5.0 > > > 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 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3628) Add property expansion capability to .wsdl files

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3628: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Add property expansion capability to .wsdl files > ------------------------------------------------ > > Key: JBWS-3628 > URL: https://issues.jboss.org/browse/JBWS-3628 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: david.boeren > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-5.0 > > > The customer is doing JMS-based webservices using the following declarations in their wsdl file (referred to using the wsdllocation annotation): > <soapjms:jndiConnectionFactoryName>myqueue</soapjms:jndiConnectionFactoryName> <soapjms:jndiInitialContextFactory>com.vendor.InitialContextFactory</soapjms:jndiInitialContextFactory> > <soapjms:jndiURL>$MY_URL</soapjms:jndiURL> > The $MY_URL is the url of the messaging server. Since property replacement does not work for wsdl files they need to manually modify this before deploying and package separate versions of their app for each environment. If property expansion worked in the .wsdl this would no longer be necessary. -- 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, 3 months

1
0
0 / 0

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3777?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3777: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > 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 > 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 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3764) MarshallTestCase leaks

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3764?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3764: -------------------------------- Checked-in Bartosz's patch. http://svn.jboss.org/repos/jbossws/stack/native/branches/jbossws-native-3... Subversion: Committed revision 18555. (I was not able to reproduce the issue before applying the patch.) > MarshallTestCase leaks > ---------------------- > > Key: JBWS-3764 > URL: https://issues.jboss.org/browse/JBWS-3764 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.1.2, jbossws-native-3.4.1 > Reporter: Bartosz Baranowski > Assignee: Alessio Soldano > Attachments: JBWS-3764.patch > > > Due to design, MarshalTestCase leaks HRef setup. Depending on method execution order it may pass or fail. -- 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, 3 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 2014