May 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3919) Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3919?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3919: --------------------------------------- This could simply be a bug in those cxf lines or because of a TCK check actually requiring it. We'll figure out what can be done. > Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers > ------------------------------------------------------------------------------------------ > > Key: JBWS-3919 > URL: https://issues.jboss.org/browse/JBWS-3919 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Takashi Nishigaya > Fix For: jbossws-cxf-5.1 > > Attachments: handler_header_chain.zip > > > CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance, > 1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context. > 2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null. > The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services. > The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers. > Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case. > In order to reproduce the issue: > $ mvm clean test -P wildly-managed (or -P wildly-remote) > Additionally, this behavior is the same in EAP 6.3.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3919) Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3919?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3919: ---------------------------------- Assignee: (was: Alessio Soldano) > Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers > ------------------------------------------------------------------------------------------ > > Key: JBWS-3919 > URL: https://issues.jboss.org/browse/JBWS-3919 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Takashi Nishigaya > Fix For: jbossws-cxf-5.1 > > Attachments: handler_header_chain.zip > > > CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance, > 1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context. > 2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null. > The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services. > The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers. > Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case. > In order to reproduce the issue: > $ mvm clean test -P wildly-managed (or -P wildly-remote) > Additionally, this behavior is the same in EAP 6.3.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3919) Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3919?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3919: ---------------------------------- Fix Version/s: jbossws-cxf-5.1 > Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers > ------------------------------------------------------------------------------------------ > > Key: JBWS-3919 > URL: https://issues.jboss.org/browse/JBWS-3919 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Takashi Nishigaya > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > Attachments: handler_header_chain.zip > > > CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance, > 1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context. > 2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null. > The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services. > The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers. > Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case. > In order to reproduce the issue: > $ mvm clean test -P wildly-managed (or -P wildly-remote) > Additionally, this behavior is the same in EAP 6.3.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3919) Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3919?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3919: ---------------------------------- Project: JBoss Web Services (was: WildFly) Key: JBWS-3919 (was: WFLY-4393) Workflow: classic default workflow (was: GIT Pull Request workflow ) Affects Version/s: (was: 8.2.0.Final) Component/s: jbossws-cxf (was: Web Services) > Client-side message context value HTTP_REQUEST_HEADERS is not shared between SOAP handlers > ------------------------------------------------------------------------------------------ > > Key: JBWS-3919 > URL: https://issues.jboss.org/browse/JBWS-3919 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Takashi Nishigaya > Assignee: Alessio Soldano > Attachments: handler_header_chain.zip > > > CXF runtime does NOT propagate JAX-WS standard context value MessageContext.HTTP_REQUEST_HEADERS to the subsequent client-side SOAP handlers. For instance, > 1. The first client handler puts the newly created HTTP request header map that contains the custom header 'foo' in the message context. > 2. The second client handler can not refer to the custom header 'foo' added in the step 1. The HTTP request header map in the message context is null. > The weird thing is that the custom header added in the step 1 is correctly received by the server-side web services. > The both of Java SE default JAX-WS implementations and GlassFish correctly share HTTP_REQUEST_HEADERS map between handlers. > Please check the attached test case and compare the two test case. The method testHandlerChainOnServer() tests the case that the client is running on the container. On the other hand, testHandlerChainOnStandalone() tests the standalone client case. > In order to reproduce the issue: > $ mvm clean test -P wildly-managed (or -P wildly-remote) > Additionally, this behavior is the same in EAP 6.3.3. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3916) Remove the workaround for JBWS-3843

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3916?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3916: --------------------------------------- Thanks Ivo; any chance you or Jim can tell which is the first version of WildFly that was affected by the issue fixed inWFLY-4625? JBossWS supports multiple target containers (https://developer.jboss.org/wiki/JBossWS-SupportedTargetContainers), so the workaround will be actually removable when all the supported containers will be fixed. > Remove the workaround for JBWS-3843 > ----------------------------------- > > Key: JBWS-3916 > URL: https://issues.jboss.org/browse/JBWS-3916 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-integration > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Ivo Studensky > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > The work-around for JBWS-3843 is no longer needed due to a change made in WFLY-4625. It might be reverted for the next version dedicated to WildFly, i.e. 5.1.0.Final. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3917) Wrong help message in wsconsume.bat

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3917?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3917: --------------------------------------- Looks like WFLY-2109... > Wrong help message in wsconsume.bat > ----------------------------------- > > Key: JBWS-3917 > URL: https://issues.jboss.org/browse/JBWS-3917 > Project: JBoss Web Services > Issue Type: Bug > Components: tools-jaxws > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Marek Kopecký > Priority: Minor > Fix For: jbossws-cxf-5.1 > > > Description of problem: > Help message in wsconsume.bat contains wrong "usage" section. > How reproducible: > Always on Windows > Steps to Reproduce: > 1. wsconsume.bat -h > Actual results: > ... > usage: org.jboss.ws.tools.cmd.WSConsume [options] <wsdl-url> > ... > Expected results on Windows: > ... > usage: wsconsume.bat [options] <wsdl-url> > ... > Additional info: > On linux: > ./wsconsume.sh -h > ... > usage: wsconsume.sh [options] <wsdl-url> > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3918) Unify help message in wsprovide.bat and wsprovide.sh

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3918?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3918: ---------------------------------- Fix Version/s: jbossws-cxf-5.1 > Unify help message in wsprovide.bat and wsprovide.sh > ---------------------------------------------------- > > Key: JBWS-3918 > URL: https://issues.jboss.org/browse/JBWS-3918 > Project: JBoss Web Services > Issue Type: Bug > Components: tools-jaxws > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Marek Kopecký > Priority: Minor > Fix For: jbossws-cxf-5.1 > > > Description of problem: > Unify help message in wsprovide.bat and wsprovide.sh > Steps to Reproduce: > 1. On windows: wsconsume.bat -h > 2. On linux: wsconsume.sh -h > Actual results: > On windows: > ... > usage: WSProvide [options] <endpoint class name> > ... > On linux: > ... > usage: wsprovide.sh [options] <endpoint class name> > ... > Expected results on Windows: > ... > usage: wsprovide.bat [options] <endpoint class name> > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3917) Wrong help message in wsconsume.bat

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3917?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3917: ---------------------------------- Fix Version/s: jbossws-cxf-5.1 > Wrong help message in wsconsume.bat > ----------------------------------- > > Key: JBWS-3917 > URL: https://issues.jboss.org/browse/JBWS-3917 > Project: JBoss Web Services > Issue Type: Bug > Components: tools-jaxws > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Marek Kopecký > Priority: Minor > Fix For: jbossws-cxf-5.1 > > > Description of problem: > Help message in wsconsume.bat contains wrong "usage" section. > How reproducible: > Always on Windows > Steps to Reproduce: > 1. wsconsume.bat -h > Actual results: > ... > usage: org.jboss.ws.tools.cmd.WSConsume [options] <wsdl-url> > ... > Expected results on Windows: > ... > usage: wsconsume.bat [options] <wsdl-url> > ... > Additional info: > On linux: > ./wsconsume.sh -h > ... > usage: wsconsume.sh [options] <wsdl-url> > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3918) Unify help message in wsprovide.bat and wsprovide.sh

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/JBWS-3918?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated JBWS-3918: -------------------------------- Project: JBoss Web Services (was: JBoss Enterprise Application Platform) Key: JBWS-3918 (was: JBEAP-171) Workflow: classic default workflow (was: CDW v1) Status: Open (was: New) Affects Version/s: jbossws-cxf-5.0.0.Final (was: EAP 7.0.0.DR2) Component/s: tools-jaxws (was: Web Services) Target Release: (was: EAP 7.0.0.GA) > Unify help message in wsprovide.bat and wsprovide.sh > ---------------------------------------------------- > > Key: JBWS-3918 > URL: https://issues.jboss.org/browse/JBWS-3918 > Project: JBoss Web Services > Issue Type: Bug > Components: tools-jaxws > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Marek Kopecký > Assignee: Marek Kopecký > Priority: Minor > > Description of problem: > Unify help message in wsprovide.bat and wsprovide.sh > Steps to Reproduce: > 1. On windows: wsconsume.bat -h > 2. On linux: wsconsume.sh -h > Actual results: > On windows: > ... > usage: WSProvide [options] <endpoint class name> > ... > On linux: > ... > usage: wsprovide.sh [options] <endpoint class name> > ... > Expected results on Windows: > ... > usage: wsprovide.bat [options] <endpoint class name> > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3918) Unify help message in wsprovide.bat and wsprovide.sh

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/JBWS-3918?page=com.atlassian.jira.plugin.... ] Marek Kopecký updated JBWS-3918: -------------------------------- Assignee: (was: Marek Kopecký) > Unify help message in wsprovide.bat and wsprovide.sh > ---------------------------------------------------- > > Key: JBWS-3918 > URL: https://issues.jboss.org/browse/JBWS-3918 > Project: JBoss Web Services > Issue Type: Bug > Components: tools-jaxws > Affects Versions: jbossws-cxf-5.0.0.Final > Reporter: Marek Kopecký > Priority: Minor > > Description of problem: > Unify help message in wsprovide.bat and wsprovide.sh > Steps to Reproduce: > 1. On windows: wsconsume.bat -h > 2. On linux: wsconsume.sh -h > Actual results: > On windows: > ... > usage: WSProvide [options] <endpoint class name> > ... > On linux: > ... > usage: wsprovide.sh [options] <endpoint class name> > ... > Expected results on Windows: > ... > usage: wsprovide.bat [options] <endpoint class name> > ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 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 May 2015