October 2013 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3724) Disable HTTP chunked encoding in server side

by Julio Ynojosa (JIRA)

[ https://issues.jboss.org/browse/JBWS-3724?page=com.atlassian.jira.plugin.... ] Julio Ynojosa commented on JBWS-3724: ------------------------------------- The option you mention was discarded because in HTTP 1.0 new connections are open for each request/response pair. And after each response the connection would be closed. This lead to some big efficiency problems. I asked to several people and they do not recommend do this. I disabled Chunked encoding in client side, over HTTP 1.1 and i was hoping to do the same in server side, keeping HTTP 1.1 because it means that chunked transfer encoding is an option in HTTP 1.1 > Disable HTTP chunked encoding in server side > -------------------------------------------- > > Key: JBWS-3724 > URL: https://issues.jboss.org/browse/JBWS-3724 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Affects Versions: jbossws-native-3.4.0 > Reporter: Julio Ynojosa > Priority: Minor > > I've always seen that to disable chunking encoding is always related to client configuration. How can it be disabled from server side? What configuration file can be changed in JBoss or JBossWS to do that? > I disabled the "Chunked Transfer encoding" mechanism from clients to server through a external library (AXIS2, client side). Now I need to do the same from server to clients (server responses, i.e. server side) to ensure both requests and responses are being sent without fragmentation. > > According to documentation, I have configured the parameter "chunked size" to zero (to get no fragmentation) in the "standard-jaxws-client-config.xml" file and also updated JBossWS library to 3.4.0 version (higher version compatible with JBoss 5) and yet I haven’t been able to deactivate the Chunking mechanism. It is reported that this was an issue, but it was supposed to be solved since JBossWS 3.2.0 > Is it anything additional that do I have to do in order to get this problem solved? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3663) Remove eclipse warnings

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3663?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3663: --------------------------------------- Fixed on trunk. > Remove eclipse warnings > ----------------------- > > Key: JBWS-3663 > URL: https://issues.jboss.org/browse/JBWS-3663 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Minor > Fix For: jbossws-cxf-4.3 > > Attachments: patch_jbossws_4.1.x_trunk_modules_testsuite_eclipse_warnings.v1.txt, patch_jbossws_cxf_trunk_modules_client_eclipse_warnings.txt, patch_jbossws_cxf_trunk_modules_modules_addons_transports_http_httpserver_eclipse_warnings.txt, patch_jbossws_cxf_trunk_modules_server_eclipse_warnings.txt, patch_jbossws_cxf_trunk_modules_testsuite_eclipse_warnings.v1.txt, patch_jbossws_cxf_trunk_modules_testsuite_eclipse_warnings_part_2.txt, patch_jbossws_cxf_trunk_modules_testsuite_eclipse_warnings_part_3.txt, patch_jbossws_shared_testsuite_4.1.x_eclipse_warnings.v1.txt > > > Remove eclipse warnings in modules/testsuite. Patch handles warnings related to unused import, generics, etc. Few warnings left should be checked / handled separately case by case if possible. > Attached patches for branck 4.1.x and for trunk -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3630) Enable CXF Asynch Client HTTP transport

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3630?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3630: ---------------------------------- Fix Version/s: jbossws-cxf-4.3 > Enable CXF Asynch Client HTTP transport > --------------------------------------- > > Key: JBWS-3630 > URL: https://issues.jboss.org/browse/JBWS-3630 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > Starting from 2.7.x series, Apache CXF provides an additional asynch http client implementation: http://cxf.apache.org/docs/asynchronous-client-http-transport.html > The new transport is built on top of Apache HTTP Components HttpAsyncClient (http://hc.apache.org/httpcomponents-asyncclient-dev/index.html) and is automatically enabled (currently for asynch calls only) whenever the cxf-rt-transports-http-hc component is available. That is currently excluded from the dependency tree and not installed on the JBoss AS / WildFly as the HttpAsyncClient it transitively depends on is still at Beta level. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3717) EndpointResolver implementations do not verify endpoint state before using endpoint

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3717?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3717: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550] from MODIFIED to ON_QA > EndpointResolver implementations do not verify endpoint state before using endpoint > ----------------------------------------------------------------------------------- > > Key: JBWS-3717 > URL: https://issues.jboss.org/browse/JBWS-3717 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > Currently the implementors of EndpointResolver (namely, WebAppResolver and PortComponentResolver do not check the state of an endpoint before trying using it. This is a problem as with JBWS-3643 the EndpointRegistry is now based on the AS service registry, so it's possible for the resolvers to see endpoints that are not started yet. The issue would likely affect scenarios with frequent and concurrent deploy/undeploy sequences or requests reaching the AS during boot. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3719) ServiceContainerEndpointRegistry#getRegisteredEndpoints() returns set containing null

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3719?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3719: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1017550|https://bugzilla.redhat.com/show_bug.cgi?id=1017550] from MODIFIED to ON_QA > ServiceContainerEndpointRegistry#getRegisteredEndpoints() returns set containing null > ------------------------------------------------------------------------------------- > > Key: JBWS-3719 > URL: https://issues.jboss.org/browse/JBWS-3719 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration, jbossws-native > Affects Versions: jbossws-cxf-4.2 > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.2.2 > > > The ServiceContainerEndpointRegistry#getRegisteredEndpoints() can return a set containing null as the retrieval of the service list from the container service registry plus the lookup of each service corresponding to the name is not atomic. We need to protect against this, as the consumers of org.jboss.wsf.spi.management.EndpointRegistry#resolve(EndpointResolver resolver) choke on it with NPEs. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3690) XMLJavaTypeAdapter not working in Exception Classes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3690?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3690: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 999893|https://bugzilla.redhat.com/show_bug.cgi?id=999893] from MODIFIED to ON_QA > XMLJavaTypeAdapter not working in Exception Classes > --------------------------------------------------- > > Key: JBWS-3690 > URL: https://issues.jboss.org/browse/JBWS-3690 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.2 > Reporter: Mustafa Musaji > Assignee: Mustafa Musaji > Fix For: jbossws-cxf-4.2.2 > > Attachments: cxf5219.diff, cxfTest.jar > > > @XMLJavaTypeAdapter usage in Exception Classes does not work when mapping to a class not in the JAXB Context. > {code:title=MyEJB.java} > @Stateless > @WebService > public class MyEJB { > public void launcheMyException() throws MyException { > return; > } > } > {code} > {code:title=MyException.java} > @XmlAccessorType(XmlAccessType.FIELD) > public class MyException extends Exception { > @XmlJavaTypeAdapter(Cl1ToCl2Adapter.class) > MyClass1 obj1; > @XmlJavaTypeAdapter(NoArgObjAdapter.class) > NoArgObj obj2; > public MyClass1 getObj1() { > return obj1; > } > > public void setObj1(MyClass1 obj1) { > this.obj1 = obj1; > } > public NoArgObj getObj2() { > return obj2; > } > public void setObj2(NoArgObj obj2) { > this.obj2 = obj2; > } > } > {code} > {code:title=Cl1ToCl2Adapter.java} > public class Cl1ToCl2Adapter extends XmlAdapter<MyClass2,MyClass1> { > @Override > public MyClass2 marshal(MyClass1 v) throws Exception { > return new MyClass2(); > } > @Override > public MyClass1 unmarshal(MyClass2 v) throws Exception { > MyClass1 mc1 = new MyClass1(v.getS2()); > return mc1; > } > } > {code} > This is what the resulting WSDL contains. Obj2 is mapped fine to a String, but MyClass1 is not and should have the MyClass2 mapping here. > {code:xml} > <xs:complexType name="MyException"> > <xs:sequence> > <xs:element name="str" nillable="true" type="xs:string"/> > <xs:element name="obj2" nillable="true" type="xs:string"/> > </xs:sequence> > </xs:complexType> > {code} > If you add the same adapter to a non Exception class it works just fine. > This is NOT a duplicate of JBWS-3552 as I believe in that use case only known JAXB types were tested (HashMap, Strings etc). This issue is when you are using custom classes that need to be mapped. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3725) Set verify-client flag on htts listener in WSSecurityPolicyExamples23xTestCase

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3725?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3725: --------------------------------------- https://github.com/wildfly/wildfly/pull/5380 > Set verify-client flag on htts listener in WSSecurityPolicyExamples23xTestCase > ------------------------------------------------------------------------------ > > Key: JBWS-3725 > URL: https://issues.jboss.org/browse/JBWS-3725 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3 > > > With the latest changes in WFLY master, we need to explicitly setup the server https listener verify-client flag in WSSecurityPolicyExamples23xTestCase . -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3725) Set verify-client flag on htts listener in WSSecurityPolicyExamples23xTestCase

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3725: ------------------------------------- Summary: Set verify-client flag on htts listener in WSSecurityPolicyExamples23xTestCase Key: JBWS-3725 URL: https://issues.jboss.org/browse/JBWS-3725 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.3 With the latest changes in WFLY master, we need to explicitly setup the server https listener verify-client flag in WSSecurityPolicyExamples23xTestCase . -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3724) Disable HTTP chunked encoding in server side

by Julio Ynojosa (JIRA)

Julio Ynojosa created JBWS-3724: ----------------------------------- Summary: Disable HTTP chunked encoding in server side Key: JBWS-3724 URL: https://issues.jboss.org/browse/JBWS-3724 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.0 Reporter: Julio Ynojosa Priority: Minor I've always seen that to disable chunking encoding is always related to client configuration. How can it be disabled from server side? What configuration file can be changed in JBoss or JBossWS to do that? I disabled the "Chunked Transfer encoding" mechanism from clients to server through a external library (AXIS2, client side). Now I need to do the same from server to clients (server responses, i.e. server side) to ensure both requests and responses are being sent without fragmentation. According to documentation, I have configured the parameter "chunked size" to zero (to get no fragmentation) in the "standard-jaxws-client-config.xml" file and also updated JBossWS library to 3.4.0 version (higher version compatible with JBoss 5) and yet I haven’t been able to deactivate the Chunking mechanism. It is reported that this was an issue, but it was supposed to be solved since JBossWS 3.2.0 Is it anything additional that do I have to do in order to get this problem solved? -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-2694) Enable simpler approach to disable chunked encoding

by Julio Ynojosa (JIRA)

[ https://issues.jboss.org/browse/JBWS-2694?page=com.atlassian.jira.plugin.... ] Julio Ynojosa commented on JBWS-2694: ------------------------------------- I've always seen that to disable chunking encoding is always related to client configuration. How can it be disabled from server side? What configuration file can be changed in JBoss or JBossWS to do that? > Enable simpler approach to disable chunked encoding > --------------------------------------------------- > > Key: JBWS-2694 > URL: https://issues.jboss.org/browse/JBWS-2694 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jbossws-native > Reporter: Darran Lofthouse > Assignee: Alessio Soldano > Fix For: jbossws-native-3.2.0 > > > By default JBossWS will send messages using chunked encoding, however a number of servers, proxy servers and load balancers do not support chunked encoding. > The setting to disable this is not simple as it is in the configuration, this should be made simpler by also allowing it to be disabled on the request context as well. -- 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

11 years, 1 month

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 October 2013