March 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3890) Enhance EndpointMetrics api to collect the concurrent request count and endpoint method request count information

by Jim Ma (JIRA)

Jim Ma created JBWS-3890: ---------------------------- Summary: Enhance EndpointMetrics api to collect the concurrent request count and endpoint method request count information Key: JBWS-3890 URL: https://issues.jboss.org/browse/JBWS-3890 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf Affects Versions: jbossws-cxf-5.0.0.Beta3 Reporter: Jim Ma Assignee: Jim Ma -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3889) Fix test failures with IPv6

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3889: ------------------------------------- Summary: Fix test failures with IPv6 Key: JBWS-3889 URL: https://issues.jboss.org/browse/JBWS-3889 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, productization Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 See e.g. http://jbossws-qa.jboss.org:8180/hudson/job/CXF-CORE-AS-8.2.0-IPV6/1/test... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3888) metadata-complete setting ignored

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3888: ------------------------------------- Summary: metadata-complete setting ignored Key: JBWS-3888 URL: https://issues.jboss.org/browse/JBWS-3888 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0 See https://developer.jboss.org/message/921776 . We need to check if metadata-complete setting is being properly considered and if it's not, fix it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

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

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created JBWS-3887: ---------------------------------------- Summary: 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.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3882) Add IPv6 jobs to Hudson

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3882?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3882: ---------------------------------- Assignee: Alessio Soldano > Add IPv6 jobs to Hudson > ----------------------- > > Key: JBWS-3882 > URL: https://issues.jboss.org/browse/JBWS-3882 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > Use the following command line options: > {noformat} > -Djboss.bind.address=[::1] -DadditionalJvmArgs="-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true" -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3879) Convention for declaring interceptor and feature parameters through properties

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3879?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3879: ---------------------------------- Description: JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below: ||Property||Value|| |cxf.features|##foo, ##bar| |##foo|org.apache.cxf.feature.GZIPFeature| |##foo.threshold|0| |##bar|org.apache.cxf.feature.RMFeature| was: JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below: ||Property||Value|| |cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar| |org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature| |org.jboss.ws.cxf.DelegateFeature.foo.threshold|0| |org.jboss.ws.cxf.DelegateFeature.bar.class|org.apache.cxf.feature.RMFeature| > Convention for declaring interceptor and feature parameters through properties > ------------------------------------------------------------------------------ > > Key: JBWS-3879 > URL: https://issues.jboss.org/browse/JBWS-3879 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below: > ||Property||Value|| > |cxf.features|##foo, ##bar| > |##foo|org.apache.cxf.feature.GZIPFeature| > |##foo.threshold|0| > |##bar|org.apache.cxf.feature.RMFeature| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3879) Convention for declaring interceptor and feature parameters through properties

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3879?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3879: --------------------------------------- https://docs.jboss.org/author/display/JBWS/Apache+CXF+integration#ApacheC... > Convention for declaring interceptor and feature parameters through properties > ------------------------------------------------------------------------------ > > Key: JBWS-3879 > URL: https://issues.jboss.org/browse/JBWS-3879 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > JBWS-3837, JBWS-3840, JBWS-3875 allow setting CXF interceptors and features through properties. We need a convention for setting parameters values in case of complex properties. A proposal is to use properties as in the example below: > ||Property||Value|| > |cxf.features|org.jboss.ws.cxf.DelegateFeature.foo, org.apache.cxf.DelegateFeature.bar| > |org.jboss.ws.cxf.DelegateFeature.foo.class|org.apache.cxf.feature.GZIPFeature| > |org.jboss.ws.cxf.DelegateFeature.foo.threshold|0| > |org.jboss.ws.cxf.DelegateFeature.bar.class|org.apache.cxf.feature.RMFeature| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3886) Add option for easily testing with IPv6

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3886: ------------------------------------- Summary: Add option for easily testing with IPv6 Key: JBWS-3886 URL: https://issues.jboss.org/browse/JBWS-3886 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 Currently, the following options have to be provided on command line to test using IPv6: {noformat} -DadditionalJvmArgs="-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true" -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true {noformat} We should have a shortcut / simpler option, perhaps through a dedicated maven profile. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3863) @MTOM.enabled is not honored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3863?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3863: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1178234|https://bugzilla.redhat.com/show_bug.cgi?id=1178234] from ASSIGNED to NEW > @MTOM.enabled is not honored > ---------------------------- > > Key: JBWS-3863 > URL: https://issues.jboss.org/browse/JBWS-3863 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3.1 > Reporter: Kyle Lape > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta3 > > Attachments: jbws3863.diff > > > If you put {{@MTOM(enabled=false)}} on an endpoint, it will still send responses as if MTOM is enabled. If you remove the annotation altogether, the endpoint will end up inlining the content as you'd expect. This does not occur if you run CXF standalone -- only when using the JBossWS integration layer in JBoss. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBWS-3863) @MTOM.enabled is not honored

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBWS-3863?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBWS-3863: ----------------------------------------------- Panagiotis Sotiropoulos <psotirop(a)redhat.com> changed the Status of [bug 1178234|https://bugzilla.redhat.com/show_bug.cgi?id=1178234] from NEW to ASSIGNED > @MTOM.enabled is not honored > ---------------------------- > > Key: JBWS-3863 > URL: https://issues.jboss.org/browse/JBWS-3863 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3.1 > Reporter: Kyle Lape > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.0.Beta3 > > Attachments: jbws3863.diff > > > If you put {{@MTOM(enabled=false)}} on an endpoint, it will still send responses as if MTOM is enabled. If you remove the annotation altogether, the endpoint will end up inlining the content as you'd expect. This does not occur if you run CXF standalone -- only when using the JBossWS integration layer in JBoss. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

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