June 2014 - jbossws-issues - Jboss List Archives

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

by Tadayoshi Sato (JIRA)

[ https://issues.jboss.org/browse/JBWS-3802?page=com.atlassian.jira.plugin.... ] Tadayoshi Sato updated JBWS-3802: --------------------------------- Description: 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. was: Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue. 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. > 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 > > 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)

10 years, 6 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 Tadayoshi Sato (JIRA)

Tadayoshi Sato created JBWS-3802: ------------------------------------ Summary: 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.3, jbossws-cxf-4.2.4 Reporter: Tadayoshi Sato Please port [CXF-5810|https://issues.apache.org/jira/browse/CXF-5810], which is the root cause of the issue. 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)

10 years, 6 months

1
0
0 / 0

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

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3628?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3628: -------------------------------- This will not work because CXF is inspecting the @WebService annotation to retrieve path to the wsdl and then extracting the wsdl from the archive. There is no way for us to pass information about an altered wsdl file written to disk or an InputStream to said file. I recommend we request cxf to allow us to pass a filter class through the bus extensions map, that cxf runs immediately after they read the wsdl into the Definition class. Our filter class will post process the contents of the Definition class before subsequent cxf processing. > 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: R Searls > 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 was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[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: ----------------------------------------------- Vaclav Tunka <vtunka(a)redhat.com> changed the Status of [bug 1077262|https://bugzilla.redhat.com/show_bug.cgi?id=1077262] from MODIFIED to ON_QA > 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)

10 years, 6 months

1
0
0 / 0

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

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3750?page=com.atlassian.jira.plugin.... ] R Searls updated JBWS-3750: --------------------------- Attachment: feature-doc-fragment.txt Documentation fragment to be added to on-line guides when feature becomes publicly available. > 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)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3801) Ensure wsdl written to filesystem as per JSR-109 requirement uses properly rewritten soap:address

by R Searls (JIRA)

[ https://issues.jboss.org/browse/JBWS-3801?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3801: -------------------------------- New test modules/testsuite/shared-tests/src/test/java/org/jboss/test/ws/jaxws/jbws2150/JBWS2150WsdlContentsTestCaseForked.java checked into repo, https://svn.jboss.org/repos/jbossws/stack/cxf/branches/rsearls. Test should be integrated into trunk in conjunction with JBWS-3750 integration. > Ensure wsdl written to filesystem as per JSR-109 requirement uses properly rewritten soap:address > ----------------------------------------------------------------------------------------------------- > > Key: JBWS-3801 > URL: https://issues.jboss.org/browse/JBWS-3801 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: R Searls > Assignee: R Searls > Priority: Minor > > In relationship to JBWS-3750, create a set of tests that verifies that a custom WSDLGetUtils class that implements method updateCodeFirstSoapAddress writes the proper data to the wsdl file on disk. > This is dependent upon access of JBossWS intergration of CXF version 3.0.1 or 2.7.12 later and intgration of changed for rsearls code tagged branchs into (JBossWS) cxf/trunk -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3530: --------------------------------------- Related forum thread: https://community.jboss.org/thread/241209 > Add some hints to the code generated by cxf using wsconsume to tune generated code before use > --------------------------------------------------------------------------------------------- > > Key: JBWS-3530 > URL: https://issues.jboss.org/browse/JBWS-3530 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBossWS CXF > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Trivial > Labels: webservices > Fix For: jbossws-cxf-5.0 > > > The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized. > {code:title=WSService.java|borderStyle=solid} > static { > URL url = null; > try { > url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } catch (MalformedURLException e) { > java.util.logging.Logger.getLogger(WSProviderService.class.getName()) > .log(java.util.logging.Level.INFO, > "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } > WSDL_LOCATION = url; > } > {code} > This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3530: --------------------------------------- So, in few words, run {noformat}wsconsume.sh -k -w <desired_wsdl_location_url> <local_wsdl_location>{noformat} where <desired_wsdl_location_url> is the url you want to see in @WebServiceClient wsdlLocation attribute and in the URL within the try-catch block above, while <local_wsdl_location> is the location to actually read the wsdl from and generate the code. > Add some hints to the code generated by cxf using wsconsume to tune generated code before use > --------------------------------------------------------------------------------------------- > > Key: JBWS-3530 > URL: https://issues.jboss.org/browse/JBWS-3530 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBossWS CXF > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Trivial > Labels: webservices > Fix For: jbossws-cxf-5.0 > > > The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized. > {code:title=WSService.java|borderStyle=solid} > static { > URL url = null; > try { > url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } catch (MalformedURLException e) { > java.util.logging.Logger.getLogger(WSProviderService.class.getName()) > .log(java.util.logging.Level.INFO, > "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } > WSDL_LOCATION = url; > } > {code} > This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3530 at 6/13/14 4:18 AM: ---------------------------------------------------------------- Self note: check if -wsdllocation option of wsconsume can be of any help here > Add some hints to the code generated by cxf using wsconsume to tune generated code before use > --------------------------------------------------------------------------------------------- > > Key: JBWS-3530 > URL: https://issues.jboss.org/browse/JBWS-3530 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.0.2 > Environment: JBossWS CXF > Reporter: Mustafa Musaji > Assignee: Jim Ma > Priority: Trivial > Labels: webservices > Fix For: jbossws-cxf-5.0 > > > The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized. > {code:title=WSService.java|borderStyle=solid} > static { > URL url = null; > try { > url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } catch (MalformedURLException e) { > java.util.logging.Logger.getLogger(WSProviderService.class.getName()) > .log(java.util.logging.Level.INFO, > "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl"); > } > WSDL_LOCATION = url; > } > {code} > This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3801) Ensure wsdl written to filesystem as per JSR-109 requirement uses properly rewritten soap:address

by R Searls (JIRA)

R Searls created JBWS-3801: ------------------------------ Summary: Ensure wsdl written to filesystem as per JSR-109 requirement uses properly rewritten soap:address Key: JBWS-3801 URL: https://issues.jboss.org/browse/JBWS-3801 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: R Searls Assignee: R Searls Priority: Minor In relationship to JBWS-3750, create a set of tests that verifies that a custom WSDLGetUtils class that implements method updateCodeFirstSoapAddress writes the proper data to the wsdl file on disk. This is dependent upon access of JBossWS intergration of CXF version 3.0.1 or 2.7.12 later and intgration of changed for rsearls code tagged branchs into (JBossWS) cxf/trunk -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 6 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 June 2014