July 2015 - jbossws-issues - Jboss List Archives

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

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3903?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3903: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.0.Final (was: jbossws-cxf-5.1.0.Beta1) > 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 > Fix For: jbossws-cxf-5.1.0.Final > > > 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 (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3935) Move jbossws-qa.jboss.org to a recent Jenkins version

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3935: ------------------------------------- Summary: Move jbossws-qa.jboss.org to a recent Jenkins version Key: JBWS-3935 URL: https://issues.jboss.org/browse/JBWS-3935 Project: JBoss Web Services Issue Type: Task Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3934) Add WildFly 8.2.1.Final and 9.0.1.Final as supported target containers

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3934?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3934: ---------------------------------- Assignee: Alessio Soldano > Add WildFly 8.2.1.Final and 9.0.1.Final as supported target containers > ---------------------------------------------------------------------- > > Key: JBWS-3934 > URL: https://issues.jboss.org/browse/JBWS-3934 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0.1.Final, jbossws-cxf-5.1.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3870) Imported schemas in weird places in deployments causes issues

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3870?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3870: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.0.Final (was: jbossws-cxf-5.1.0.Beta1) > Imported schemas in weird places in deployments causes issues > ------------------------------------------------------------- > > Key: JBWS-3870 > URL: https://issues.jboss.org/browse/JBWS-3870 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: R Searls > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.0.Final > > Attachments: schemasInWeirdPlaceFromSrc.zip > > > There is a customer that has placed their WSDL files under > WEB-INF/classes/wsdl rather than just WEB-INF/wsdl. They then put > their WSDL under a subdirectory of that folder, say "thewsdl". Then > that WSDL references other schemas in other subdirectories at the same > level as the WSDL's subdirectory. Like this: > WEB-INF/ > classes/ > wsdl/ > thewsdl/ > the-actual-wsdl.wsdl > schemas/ > some-schema.xsd > When this gets deployed, all the imported schemas fall outside the > deployment's data/wsdl folder when they are written to the filesystem. > Like this: > standalone/ > data/ > wsdl/ > myDeployment.war/ > <wsdl would go here> > schemas/ > some-schema.xsd > This can cause weird concurrency issues if multiple deployment > processor threads happen to be processing separate webservices where > each have WSDLs that happen to import schemas with the same schemaLocation > attribute. In the above scenario, the schemaLocation would include a > ".." since the WSDL would be in its own subfolder. > The code that writes these files to disk is here > Line 224: > https://anonsvn.jboss.org/repos/jbossws/common/tags/jbossws-common-2.3.1.... > Line 190: > https://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.3.... > The problem is that WSDLFilePublisher.getPublishLocation() cuts off > subfolders that the WSDL is under in this particular scenario, so when > the schemaLocation that has ".." in it is appended to the WSDL path, > it will write the schema outside the deployment's data/wsdl/ folder. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 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.0.Final (was: jbossws-cxf-5.1.0.Beta1) > 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.0.Final > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3934) Add WildFly 8.2.1.Final and 9.0.1.Final as supported target containers

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3934: ------------------------------------- Summary: Add WildFly 8.2.1.Final and 9.0.1.Final as supported target containers Key: JBWS-3934 URL: https://issues.jboss.org/browse/JBWS-3934 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.0.1.Final, jbossws-cxf-5.1.0.Beta1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3907) Add ws-rm test which configures RMManager/RMStore without spring

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3907?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3907: ---------------------------------- Fix Version/s: jbossws-cxf-5.0.1 > Add ws-rm test which configures RMManager/RMStore without spring > ---------------------------------------------------------------- > > Key: JBWS-3907 > URL: https://issues.jboss.org/browse/JBWS-3907 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.0.0.CR1 > Reporter: Jim Ma > Assignee: Jim Ma > Fix For: jbossws-cxf-5.0.1, jbossws-cxf-5.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3931) Upgrade to Apache CXF 3.1.x

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3931?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3931 at 7/20/15 5:27 PM: ---------------------------------------------------------------- These are a related commit (wrong jira reference in the comment): * https://github.com/jbossws/jbossws-cxf/commit/ee4f45cb0da02fa9f4e5ff4b13c... * https://github.com/jbossws/jbossws-cxf/commit/6d5242e5bd0091366bcb90be486... was (Author: asoldano): These are a related commit (wrong jira reference in the comment): * https://github.com/jbossws/jbossws-cxf/commit/ee4f45cb0da02fa9f4e5ff4b13c... * https://github.com/jbossws/jbossws-cxf/commit/3c44511589d99b7ef92ac1d8187... > Upgrade to Apache CXF 3.1.x > --------------------------- > > Key: JBWS-3931 > URL: https://issues.jboss.org/browse/JBWS-3931 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > http://cxf.apache.org/docs/31-migration-guide.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3931) Upgrade to Apache CXF 3.1.x

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3931?page=com.atlassian.jira.plugin.... ] Alessio Soldano edited comment on JBWS-3931 at 7/20/15 5:26 PM: ---------------------------------------------------------------- These are a related commit (wrong jira reference in the comment): * https://github.com/jbossws/jbossws-cxf/commit/ee4f45cb0da02fa9f4e5ff4b13c... * https://github.com/jbossws/jbossws-cxf/commit/3c44511589d99b7ef92ac1d8187... was (Author: asoldano): This is a related commit (wrong jira reference in the comment): https://github.com/jbossws/jbossws-cxf/commit/ee4f45cb0da02fa9f4e5ff4b13c... > Upgrade to Apache CXF 3.1.x > --------------------------- > > Key: JBWS-3931 > URL: https://issues.jboss.org/browse/JBWS-3931 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > http://cxf.apache.org/docs/31-migration-guide.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3931) Upgrade to Apache CXF 3.1.x

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3931?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3931: --------------------------------------- This is a related commit (wrong jira reference in the comment): https://github.com/jbossws/jbossws-cxf/commit/ee4f45cb0da02fa9f4e5ff4b13c... > Upgrade to Apache CXF 3.1.x > --------------------------- > > Key: JBWS-3931 > URL: https://issues.jboss.org/browse/JBWS-3931 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1 > > > http://cxf.apache.org/docs/31-migration-guide.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 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 July 2015