December 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3966) Avoid calling BusFactory.setThreadDefaultBus(null) in JBossWSInvoker

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3966?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3966: ---------------------------------- Description: The invocation to Analyse if we can avoid invoking BusFactory::setThreadDefaultBus in some scenarios, to reduce contention on its THREAD_BUSSES WeakHashMap. was:Analyse if we can avoid invoking BusFactory::setThreadDefaultBus in some scenarios, to reduce contention on its THREAD_BUSSES WeakHashMap. > Avoid calling BusFactory.setThreadDefaultBus(null) in JBossWSInvoker > -------------------------------------------------------------------- > > Key: JBWS-3966 > URL: https://issues.jboss.org/browse/JBWS-3966 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > The invocation to > Analyse if we can avoid invoking BusFactory::setThreadDefaultBus in some scenarios, to reduce contention on its THREAD_BUSSES WeakHashMap. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3966) Avoid calling BusFactory.setThreadDefaultBus(null) in JBossWSInvoker

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3966?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3966: ---------------------------------- Summary: Avoid calling BusFactory.setThreadDefaultBus(null) in JBossWSInvoker (was: Reduce invocations to BusFactory::setThreadDefaultBus) > Avoid calling BusFactory.setThreadDefaultBus(null) in JBossWSInvoker > -------------------------------------------------------------------- > > Key: JBWS-3966 > URL: https://issues.jboss.org/browse/JBWS-3966 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > Analyse if we can avoid invoking BusFactory::setThreadDefaultBus in some scenarios, to reduce contention on its THREAD_BUSSES WeakHashMap. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3945) Set property that causes 400 error message to be returned by apache CXF.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3945?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3945: ----------------------------------------------- Vladimir Dosoudil <dosoudil(a)redhat.com> changed the Status of [bug 1182919|https://bugzilla.redhat.com/show_bug.cgi?id=1182919] from MODIFIED to ON_QA > Set property that causes 400 error message to be returned by apache CXF. > ------------------------------------------------------------------------ > > Key: JBWS-3945 > URL: https://issues.jboss.org/browse/JBWS-3945 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.0.Beta1 > Reporter: R Searls > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-5.1.1.Final > > > Change ./modules/client/src/main/java/org/jboss/wsf/stack/cxf/saaj/SOAPConnectionImpl.java -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3964) Incorrect behaviour with @WebParam(header = true, mode = IN)

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3964?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3964: ---------------------------------- Assignee: Jim Ma > Incorrect behaviour with @WebParam(header = true, mode = IN) > ------------------------------------------------------------ > > Key: JBWS-3964 > URL: https://issues.jboss.org/browse/JBWS-3964 > Project: JBoss Web Services > Issue Type: Bug > Environment: Wildfly 9.0.2 > Reporter: Xavier Dury > Assignee: Jim Ma > > Given the following simple WebService with incoming and outgoing header @WebParams: > {code} > @Stateless > @WebService(name = "MyEchoService", targetNamespace = "urn:echo") > public class MyEchoService { > > @WebResult(name = "result") > public String echo( > @WebParam(name = "message") String message, > @WebParam(name = "paramIn", mode = Mode.IN, header = true) Holder<String> paramIn, > @WebParam(name = "paramOut", mode = Mode.OUT, header = true) Holder<String> paramOut) { > paramOut.value = "got paramIn " + paramIn.value; > return "echo " + message; > } > } > {code} > The generated WSDL contains the following operation where the incoming @WebParam (mode = IN) is present in both input and ouput: > {code} > <wsdl:operation name="echo"> > <soap:operation soapAction="" style="document"/> > <wsdl:input name="echo"> > <soap:header message="tns:echo" part="paramIn" use="literal"></soap:header> > <soap:body parts="parameters" use="literal"/> > </wsdl:input> > <wsdl:output name="echoResponse"> > <soap:header message="tns:echoResponse" part="paramIn" use="literal"></soap:header> > <soap:header message="tns:echoResponse" part="paramOut" use="literal"></soap:header> > <soap:body parts="result" use="literal"/> > </wsdl:output> > </wsdl:operation> > {code} > We can see in the following exchange that the incoming @WebParam will be copied verbatim in the response: > {code} > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:echo"> > <soapenv:Header> > <urn:paramIn>fred</urn:paramIn> > </soapenv:Header> > <soapenv:Body> > <urn:echo> > <urn:message>hello world!</urn:message> > </urn:echo> > </soapenv:Body> > </soapenv:Envelope> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <paramIn xmlns="urn:echo">fred</paramIn> > <paramOut xmlns="urn:echo">got paramIn fred</paramOut> > </soap:Header> > <soap:Body> > <echoResponse xmlns="urn:echo"> > <result>echo hello world!</result> > </echoResponse> > </soap:Body> > </soap:Envelope> > {code} > When the incoming header @WebParam is not set, an empty element will be added to the body of the response: > {code} > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:echo"> > <soapenv:Body> > <urn:echo> > <urn:message>hello world!</urn:message> > </urn:echo> > </soapenv:Body> > </soapenv:Envelope> > <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> > <soap:Header> > <paramOut xmlns="urn:echo">got paramIn null</paramOut> > </soap:Header> > <soap:Body> > <echoResponse xmlns="urn:echo"> > <result>echo hello world!</result> > </echoResponse> > <paramIn xsi:nil="true" xmlns="urn:echo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> > </soap:Body> > </soap:Envelope> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3967) Upgrade to JAXB 2.2.11-jbossorg-1

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3967: ------------------------------------- Summary: Upgrade to JAXB 2.2.11-jbossorg-1 Key: JBWS-3967 URL: https://issues.jboss.org/browse/JBWS-3967 Project: JBoss Web Services Issue Type: Component Upgrade Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3887: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1203181|https://bugzilla.redhat.com/show_bug.cgi?id=1203181] from NEW to CLOSED > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by Ivo Studensky (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] Ivo Studensky updated JBWS-3887: -------------------------------- Assignee: Bartosz Baranowski What about this issue, is it still relevant? You stated on the referenced bz that it works. > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3887: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1203181|https://bugzilla.redhat.com/show_bug.cgi?id=1203181] from ASSIGNED to NEW > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3887: ----------------------------------------------- Ivo Studensky <istudens(a)redhat.com> changed the Status of [bug 1203181|https://bugzilla.redhat.com/show_bug.cgi?id=1203181] from NEW to ASSIGNED > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBWS-3966) Reduce invocations to BusFactory::setThreadDefaultBus

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3966: ------------------------------------- Summary: Reduce invocations to BusFactory::setThreadDefaultBus Key: JBWS-3966 URL: https://issues.jboss.org/browse/JBWS-3966 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final Analyse if we can avoid invoking BusFactory::setThreadDefaultBus in some scenarios, to reduce contention on its THREAD_BUSSES WeakHashMap. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

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 December 2015