February 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4022) Allow logging to be enabled on-the-fly

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4022?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4022: ------------------------- Fix Version/s: jbossws-cxf-5.2.4.Final Affects Version/s: jbossws-cxf-5.2.3.Final (was: jbossws-cxf-5.1.5.Final) > Allow logging to be enabled on-the-fly > -------------------------------------- > > Key: JBWS-4022 > URL: https://issues.jboss.org/browse/JBWS-4022 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.3.Final > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > Fix For: jbossws-cxf-5.2.4.Final > > > Allow the logging feature to be enabled on-the-fly without restarting the bus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4022) Allow logging to be enabled on-the-fly

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/JBWS-4022?page=com.atlassian.jira.plugin.... ] Ingo Weiss commented on JBWS-4022: ---------------------------------- [~jim.ma], apparently this made into 3.2.0 through d534ecc1d25ab4d38aaa690cb75debe9816958ee. So I think this can be resolved. > Allow logging to be enabled on-the-fly > -------------------------------------- > > Key: JBWS-4022 > URL: https://issues.jboss.org/browse/JBWS-4022 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Allow the logging feature to be enabled on-the-fly without restarting the bus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4022) Allow logging to be enabled on-the-fly

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4022?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-4022: ------------------------------ [~iweiss], What's the status of this issue ? Looks this is already included in cxf 3.2.x and can we update this issue with resolved ? > Allow logging to be enabled on-the-fly > -------------------------------------- > > Key: JBWS-4022 > URL: https://issues.jboss.org/browse/JBWS-4022 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.5.Final > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Allow the logging feature to be enabled on-the-fly without restarting the bus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3903) Automatic / dynamic test port selection

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-3903?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3903: ------------------------- Fix Version/s: (was: jbossws-cxf-5.2.5.Final) > Automatic / dynamic test port selection > --------------------------------------- > > Key: JBWS-3903 > URL: https://issues.jboss.org/browse/JBWS-3903 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Priority: Major > > Jan writes: > {quote}I think it would be nice to have some notes about ports used for testsuite run, because after move to arquillian there are many more ports used now. > Something like that because there are several different configuration being started, you need all "offsetted" ports to be free. > Reference for basic container ports: https://docs.jboss.org/author/display/WFLY8/Admin+Guide#AdminGuide-Interf... > Current offsets: > <port-offset.cxf-tests.jboss>0</port-offset.cxf-tests.jboss> > <port-offset.cxf-tests.ssl-mutual-auth>5000</port-offset.cxf-tests.ssl-mutual-auth> > <port-offset.cxf-tests.default-config-tests>10000</port-offset.cxf-tests.default-config-tests> > <port-offset.cxf-tests.jms>35000</port-offset.cxf-tests.jms> > <port-offset.shared-tests.jboss>15000</port-offset.shared-tests.jboss> > <port-offset.shared-tests.default-config-tests>20000</port-offset.shared-tests.default-config-tests> > <port-offset.shared-tests.address-rewrite>25000</port-offset.shared-tests.address-rewrite> > <port-offset.cxf-spring-tests.jboss>30000</port-offset.cxf-spring-tests.jboss> > And there are some special cases: > - org.jboss.test.ws.jaxws.endpoint.EndpointTestCase > -- where hardcoded 8081 port is used > - org.jboss.test.ws.jaxws.cxf.udp.UDPEndpointAPITestCase > -- hardcoded 9436 > - org.jboss.wsf.stack.cxf.addons.transports.udp.UDPTransportTest > -- hardcoded 9434 > - org.jboss.test.ws.jaxws.samples.wsdd.WSDiscoveryTestCase > -- 3072 port by WS-Discovery specification > {quote} > We should have something like the port utilities in org.apache.cxf.testutil.common.TestUtil (except that's not thread safe, while we need it to be thread safe to let the testsuite run with -Pfast profile). > The idea is that we could have an "ofsetted" range of ports "reserved" for the JBossWS testsuite. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4150) remove obsolete class InvocationHandlerJAXRPC from jbossws-common

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4150?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4150: ------------------------- Affects Version/s: (was: jbossws-cxf-5.2.5.Final) > remove obsolete class InvocationHandlerJAXRPC from jbossws-common > ----------------------------------------------------------------- > > Key: JBWS-4150 > URL: https://issues.jboss.org/browse/JBWS-4150 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4150) remove obsolete class InvocationHandlerJAXRPC from jbossws-common

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4150?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4150: ------------------------- Affects Version/s: jbossws-cxf-5.2.4.Final > remove obsolete class InvocationHandlerJAXRPC from jbossws-common > ----------------------------------------------------------------- > > Key: JBWS-4150 > URL: https://issues.jboss.org/browse/JBWS-4150 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: R Searls > Assignee: R Searls > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4152) Extract all versions to properties

by Jim Ma (Jira)

[ https://issues.jboss.org/browse/JBWS-4152?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-4152: ------------------------- Issue Type: Enhancement (was: Task) Component/s: jbossws-cxf Fix Version/s: jbossws-cxf-5.2.5.Final > Extract all versions to properties > ---------------------------------- > > Key: JBWS-4152 > URL: https://issues.jboss.org/browse/JBWS-4152 > Project: JBoss Web Services > Issue Type: Enhancement > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > Fix For: jbossws-cxf-5.2.5.Final > > > There are several declarations of dependencies and plugins with explicit version. We could extract all versions into properties. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4162) Enable test against wildfly1600 and drop wildfly1200

by Jim Ma (Jira)

Jim Ma created JBWS-4162: ---------------------------- Summary: Enable test against wildfly1600 and drop wildfly1200 Key: JBWS-4162 URL: https://issues.jboss.org/browse/JBWS-4162 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, jbossws-integration Affects Versions: jbossws-cxf-5.2.4.Final Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-5.2.5.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4064) Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer

by Radovan Netuka (Jira)

[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Radovan Netuka updated JBWS-4064: --------------------------------- Assignee: (was: Radovan Netuka) > Non-URL encoded Content-Id href does not seem be serialized by CXF's AttachmentSerializer > ----------------------------------------------------------------------------------------- > > Key: JBWS-4064 > URL: https://issues.jboss.org/browse/JBWS-4064 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.8.Final > Reporter: Viral Gohel > Priority: Major > Fix For: jbossws-cxf-5.2.5.Final > > Attachments: mtomExample.war > > > Check issue, https://issues.apache.org/jira/browse/CXF-7317 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4154) jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/JBWS-4154?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4154: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.5.Final > jbossws-cxf-client depends on both jboss-jaxws-api_2.2_spec and jboss-jaxws-api_2.3_spec > ---------------------------------------------------------------------------------------- > > Key: JBWS-4154 > URL: https://issues.jboss.org/browse/JBWS-4154 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jim Ma > Priority: Major > Fix For: jbossws-cxf-5.2.5.Final > > > dependency:tree goal output shows that jbossws-cxf-client (and transitively other modules too) depends on two versions of JBoss JAX-WS API: > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.3_spec:jar:1.0.0.Final:compile > The former is brought in by: > {code:java} > +- org.jboss.ws.cxf:jbossws-cxf-transports-undertow:jar:5.2.5-SNAPSHOT:compile > | \- org.jboss.ws.projects:jaxws-undertow-httpspi:jar:1.0.1.Final:compile > | +- org.jboss.spec.javax.xml.ws:jboss-jaxws-api_2.2_spec:jar:2.0.2.Final:compile > {code} > I guess we should stick to the newer one which would mean add some dependency exclude or update jaxws-undertow-httpspi to new API version stream (I vote for this) > Whole dependency tree at https://github.com/jbliznak/jbws-dependency-trees/blob/jdk11-after/jbossw... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 10 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 February 2019