May 2014 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3793) Final refactoring of jbossws-spi metadata

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3793?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3793: --------------------------------------- Classes needing changes: UnifiedServiceRefMetaData, UnifiedPortComponentRefMetaData, EJBSecurityMetaData, ... > Final refactoring of jbossws-spi metadata > ----------------------------------------- > > Key: JBWS-3793 > URL: https://issues.jboss.org/browse/JBWS-3793 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, jbossws-integration > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > When finally removing the jax-rpc support (by dropping the AS 7.2 support), we can clean-up and make immutable the last remaining metadata in jbossws-spi (org.jboss.wsf.spi.metadata.j2ee / serviceref) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3793) Final refactoring of jbossws-spi metadata

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3793: ------------------------------------- Summary: Final refactoring of jbossws-spi metadata Key: JBWS-3793 URL: https://issues.jboss.org/browse/JBWS-3793 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 When finally removing the jax-rpc support (by dropping the AS 7.2 support), we can clean-up and make immutable the last remaining metadata in jbossws-spi (org.jboss.wsf.spi.metadata.j2ee / serviceref) -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3792) JBossWS: wsdl:import always handled as relative location

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3792?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3792: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > JBossWS: wsdl:import always handled as relative location > -------------------------------------------------------- > > Key: JBWS-3792 > URL: https://issues.jboss.org/browse/JBWS-3792 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Marc H. > Fix For: jbossws-cxf-5.0 > > > As described in this thread: https://community.jboss.org/thread/240821 > wsdl:import directive seems to be always resolved as a relative location. > For example, this statement: > <wsdl:import namespace="http://foo.bar.com/foo.bar.Service" location="http://foo.bar.com/Service.svc?wsdl=wsdl0"/> > May result in this URL being resolved: > http://foo.bar.com/http://foo.bar.com/Service.svc?wsdl=wsdl0 > This prevents the WSDL file from being parsed. > This behavior seems to originate from: org.jboss.ws.common.deployment.SOAPAddressWSDLParser, line 211 in v2.3.0.Final and current trunk: > } else if (match(reader, WSDL_NS, IMPORT)) { > final String location = reader.getAttributeValue(null, LOCATION); > final String url = wsdlUrl.toString(); > final String newUrl = url.substring(0, url.lastIndexOf("/") + (location.startsWith("/") ? 0 : 1)) + location; > if (!metadata.getImports().containsKey(newUrl)) { > metadata.getImports().put(newUrl, false); > } > } -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3792) JBossWS: wsdl:import always handled as relative location

by Marc H. (JIRA)

Marc H. created JBWS-3792: ----------------------------- Summary: JBossWS: wsdl:import always handled as relative location Key: JBWS-3792 URL: https://issues.jboss.org/browse/JBWS-3792 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-4.3 Reporter: Marc H. As described in this thread: https://community.jboss.org/thread/240821 wsdl:import directive seems to be always resolved as a relative location. For example, this statement: <wsdl:import namespace="http://foo.bar.com/foo.bar.Service" location="http://foo.bar.com/Service.svc?wsdl=wsdl0"/> May result in this URL being resolved: http://foo.bar.com/http://foo.bar.com/Service.svc?wsdl=wsdl0 This prevents the WSDL file from being parsed. This behavior seems to originate from: org.jboss.ws.common.deployment.SOAPAddressWSDLParser, line 211 in v2.3.0.Final and current trunk: } else if (match(reader, WSDL_NS, IMPORT)) { final String location = reader.getAttributeValue(null, LOCATION); final String url = wsdlUrl.toString(); final String newUrl = url.substring(0, url.lastIndexOf("/") + (location.startsWith("/") ? 0 : 1)) + location; if (!metadata.getImports().containsKey(newUrl)) { metadata.getImports().put(newUrl, false); } } -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3791) Make jbossws-cxf-test-utils a top level module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3791?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3791: ---------------------------------- Description: Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuites independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under modules/testsuite is not published to the maven repository). We should hence move the jbossws-cxf-test-utils out of modules/testsuite, basically promoting it to a top-level module. was: Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuites independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under modules/testsuite is not published to the maven repository). We should hence move the jbossws-cxf-test-utils out of module/testsuite, basically promoting it to a top-level module. > Make jbossws-cxf-test-utils a top level module > ---------------------------------------------- > > Key: JBWS-3791 > URL: https://issues.jboss.org/browse/JBWS-3791 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuites independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under modules/testsuite is not published to the maven repository). > We should hence move the jbossws-cxf-test-utils out of modules/testsuite, basically promoting it to a top-level module. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3791) Make jbossws-cxf-test-utils a top level module

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3791?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3791: ---------------------------------- Description: Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuites independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under modules/testsuite is not published to the maven repository). We should hence move the jbossws-cxf-test-utils out of module/testsuite, basically promoting it to a top-level module. was: Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuite independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under module/testsuite is not published to the maven repository). We should hence move the jbossws-cxf-test-utils out of module/testsuite, basically promoting it to a top-level module. > Make jbossws-cxf-test-utils a top level module > ---------------------------------------------- > > Key: JBWS-3791 > URL: https://issues.jboss.org/browse/JBWS-3791 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf, productization > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.0 > > > Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuites independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under modules/testsuite is not published to the maven repository). > We should hence move the jbossws-cxf-test-utils out of module/testsuite, basically promoting it to a top-level module. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3791) Make jbossws-cxf-test-utils a top level module

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3791: ------------------------------------- Summary: Make jbossws-cxf-test-utils a top level module Key: JBWS-3791 URL: https://issues.jboss.org/browse/JBWS-3791 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.0 Currently the jbossws-cxf-test-utils maven module is a sub-module of the jbossws-cxf-testsuite module. That causes some minor issues like making it difficult to run one of the jbws-cxf testsuite independently and preventing external test projects (like the wsi-bp testsuites) to depend on it (because the stuff under module/testsuite is not published to the maven repository). We should hence move the jbossws-cxf-test-utils out of module/testsuite, basically promoting it to a top-level module. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3782) Allow to specify config name and additional value for JAVA_OPTS for launched appclient

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3782?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3782: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Allow to specify config name and additional value for JAVA_OPTS for launched appclient > -------------------------------------------------------------------------------------- > > Key: JBWS-3782 > URL: https://issues.jboss.org/browse/JBWS-3782 > Project: JBoss Web Services > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Affects Versions: jbossws-cxf-4.3 > Reporter: Petr Sakař > Assignee: Alessio Soldano > Priority: Optional > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > Change support for launching appclient (AppclientHelper class) > - allow to specify appclient config via -DAPPCLIENT_CONFIG_NAME > eg. -DAPPCLIENT_CONFIG_NAME=appclient.xml > - allow to append additional options to JAVA_OPTS via -DAPPCLIENT_DEBUG_OPTS > eg. -DAPPCLIENT_DEBUG_OPTS="-Xrunjdwp:transport=dt_socket,address=9787,server=y,suspend=y" > Add logging to system output -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3773) HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3773?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3773: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set > ------------------------------------------------------------------------------ > > Key: JBWS-3773 > URL: https://issues.jboss.org/browse/JBWS-3773 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > See https://issues.apache.org/jira/browse/CXF-5602 > The HttpServletContext retrieved from the WebServiceContext can have stale values when running on AS 7 (using JBossWeb) and processing WS-Addressing requests with non generic ReplyTo header props. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3784) Remove appclient-ws.xml

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3784?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3784: ---------------------------------- Fix Version/s: jbossws-cxf-5.0 > Remove appclient-ws.xml > ----------------------- > > Key: JBWS-3784 > URL: https://issues.jboss.org/browse/JBWS-3784 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-4.3.1, jbossws-cxf-5.0 > > > There's no need anymore for the appclient-ws.xml descriptor in the jbossws-cxf testsuite as there's no test actually relying on that. > The appclient-ws.xml was introduced in JBWS-3451 as a consequence of JBWS-3435, which was meant to restore the appclient tests on AS 7 series in JBossWS 4.1.0. Later, in JBWS-3565, the appclient mechanism has been revisited; as part of the process, the only two tests that were using that appclient-ws.xml were removed from the shared testsuite (https://source.jboss.org/changelog/JBossWS?cs=16994) which eventually migrated into the jbossws-cxf testuite module. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 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 May 2014