April 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3283) Provide a stax based parser of jaxws endpoint config descriptors

by Alessio Soldano (JIRA)

Provide a stax based parser of jaxws endpoint config descriptors ---------------------------------------------------------------- Key: JBWS-3283 URL: https://issues.jboss.org/browse/JBWS-3283 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.0.Beta1, jbossws-native-4.0.0.Beta1 We need a stax based parser of the jaxws endpoint config descriptors; that most probably needs to live in jbossws-spi and extend the already available org.jboss.wsf.spi.metadata.AbstractHandlerChainsMetaDataParser for the handler-chain related parsing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3282) Extend jbossws jaxws endpoint configuration (@EndpointConfig) to jbossws-cxf stack

by Alessio Soldano (JIRA)

Extend jbossws jaxws endpoint configuration (@EndpointConfig) to jbossws-cxf stack ---------------------------------------------------------------------------------- Key: JBWS-3282 URL: https://issues.jboss.org/browse/JBWS-3282 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.0.Beta1, jbossws-native-4.0.0.Beta1 This implies making the "jaxws endpoint configuration" a stack agnostic concept. See http://lists.jboss.org/pipermail/jbossws-dev/2011-April/002136.html for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3272) Upgrade to Apache CXF 2.4

by Alessio Soldano (JIRA)

Upgrade to Apache CXF 2.4 ------------------------- Key: JBWS-3272 URL: https://issues.jboss.org/browse/JBWS-3272 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Apache CXF 2.4.0 is out with a lot of changes mainly in the Bus wiring (reduction of Spring dependency) and security areas. Some the bus/spring changes are most probably equivalent to what JBossWS-CXF provides in his own customized bus factories since 3.3.x, so there's likely to be the need for removing the overlapping stuff, update the integration, etc. See https://cwiki.apache.org/confluence/display/CXF20DOC/2.4+Migration+Guide -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3135) WSTF Scenario 3 - Asynch 02 test case failure

by Alessio Soldano (JIRA)

WSTF Scenario 3 - Asynch 02 test case failure --------------------------------------------- Key: JBWS-3135 URL: https://jira.jboss.org/browse/JBWS-3135 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.4.0 The second test of the SC003 Asynch tests groups (testSc003Asynch_2 : faulting notify, MEP= OneWay, Exception=Yes, MU=no) is currently failing with jbossws-cxf stack. The reason seems to me to be in Apache CXF basically not running the out fault chain for oneway MEP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-3198) EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR

by Jim Ma (JIRA)

EPR's address is NOT used for invocations on the endpoint when the dispatchImpl is created with EPR ---------------------------------------------------------------------------------------------------- Key: JBWS-3198 URL: https://issues.jboss.org/browse/JBWS-3198 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-3.4.1, jbossws-cxf-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-4.0, jbossws-cxf-4.0 >From the jaxws api : Creates a Dispatch instance for use with objects of the user's choosing. If there are any reference parameters in the endpointReference, then those reference parameters MUST appear as SOAP headers, indicating them to be reference parameters, on all messages sent to the endpoint. The endpointReference's address MUST be used for invocations on the endpoint. In the implementation of this method, the JAX-WS runtime system takes the responsibility of selecting a protocol binding (and a port) and configuring the dispatch accordingly from the WSDL associated with this Service instance or from the metadata from the endpointReference. If this Service instance has a WSDL and the endpointReference also has a WSDL in its metadata, then the WSDL from this instance MUST be used. If this Service instance does not have a WSDL and the endpointReference does have a WSDL, then the WSDL from the endpointReference MAY be used. An implementation MUST be able to retrieve the portName from the endpointReference metadata. This method behaves the same as calling dispatch = service.createDispatch(portName, type, mode, features); where the portName is retrieved from the WSDL or EndpointReference metadata. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3185) WSTF Scenario 3 - Asynch 05/06/07/08 tests case failure

by Jim Ma (JIRA)

WSTF Scenario 3 - Asynch 05/06/07/08 tests case failure ------------------------------------------------------- Key: JBWS-3185 URL: https://issues.jboss.org/browse/JBWS-3185 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.4.1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
8
0 / 0

[JBoss JIRA] Created: (JBWS-2235) Support for multiple schemas validation

by Alessio Soldano (JIRA)

Support for multiple schemas validation --------------------------------------- Key: JBWS-2235 URL: http://jira.jboss.com/jira/browse/JBWS-2235 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jbossws-native-3.0.1 Reporter: Alessio Soldano The schema validation feature currently support one imported schema only. We should support multiple schemas instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-3278) CLONE - Support for multiple schemas validation

by Kyle Lape (JIRA)

CLONE - Support for multiple schemas validation ----------------------------------------------- Key: JBWS-3278 URL: https://issues.jboss.org/browse/JBWS-3278 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Kyle Lape Assignee: Kyle Lape Priority: Optional Fix For: jbossws-native-4.0 The schema validation feature currently support one imported schema only. We should support multiple schemas instead. The workaround is to define new schema file that imports all other schema files user want to validate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3222) Test failures due to WS scripts currently available on AS7

by Alessio Soldano (JIRA)

Test failures due to WS scripts currently available on AS7 ---------------------------------------------------------- Key: JBWS-3222 URL: https://issues.jboss.org/browse/JBWS-3222 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JBWS-3273) Move ANT & command line tools abstraction from jbossws-common.jar to jbossws-common-tools.jar

by Richard Opalka (JIRA)

Move ANT & command line tools abstraction from jbossws-common.jar to jbossws-common-tools.jar --------------------------------------------------------------------------------------------- Key: JBWS-3273 URL: https://issues.jboss.org/browse/JBWS-3273 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues April 2011