January 2011 - jbossws-issues - Jboss List Archives

[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-2882) Give setMTOMEnabled higher priority for clients

by Darran Lofthouse (JIRA)

Give setMTOMEnabled higher priority for clients ----------------------------------------------- Key: JBWS-2882 URL: https://jira.jboss.org/jira/browse/JBWS-2882 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3.0 Presently JBossWS clients call setMTOMEnabled to indicate if MTOM should be enabled for the call, however JBossWS then scans the known types for an @XmlMimeType annotation to decide if the call is eligible for MTOM. The MTOM optimisation however applies to all binary types and not just the ones annotated with @XmlMimeType. The call to setMTOMEnabled should be sufficient to enable MTOM without requiring the check for @XmlMimeType -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3186) Upgrade to Apache CXF 2.3.2

by Alessio Soldano (JIRA)

Upgrade to Apache CXF 2.3.2 --------------------------- Key: JBWS-3186 URL: https://issues.jboss.org/browse/JBWS-3186 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.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3205) java.lang.StackOverflowError on binary distro due to org.jboss.wsf.common.logging.JDKLogManager

by Alessio Soldano (JIRA)

java.lang.StackOverflowError on binary distro due to org.jboss.wsf.common.logging.JDKLogManager ----------------------------------------------------------------------------------------------- Key: JBWS-3205 URL: https://issues.jboss.org/browse/JBWS-3205 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 Testsuite: org.jboss.test.ws.console.ConsoleAccessTestCase Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec Caused an ERROR null java.lang.StackOverflowError at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:255) at java.util.logging.LogManager.getLogManager(LogManager.java:249) at java.util.logging.Logger.<init>(Logger.java:220) at org.jboss.wsf.common.logging.JDKLogger.<init>(JDKLogger.java:37) at org.jboss.wsf.common.logging.JDKLogManager.getLogger(JDKLogManager.java:40) at java.util.logging.LogManager.demandLogger(LogManager.java:390) at java.util.logging.Logger.getLogger(Logger.java:274) at org.jboss.logging.JDKLogger.<init>(JDKLogger.java:37) at org.jboss.logging.JDKLoggerProvider.getLogger(JDKLoggerProvider.java:28) at org.jboss.logging.Logger.getLogger(Logger.java:2164) at org.jboss.wsf.common.logging.JDKLogger.<init>(JDKLogger.java:39) at org.jboss.wsf.common.logging.JDKLogManager.getLogger(JDKLogManager.java:40) at java.util.logging.LogManager.demandLogger(LogManager.java:390) at java.util.logging.Logger.getLogger(Logger.java:274) ... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3084) Enable control of chunked encoding when using SOAPConnection

by Darran Lofthouse (JIRA)

Enable control of chunked encoding when using SOAPConnection ------------------------------------------------------------ Key: JBWS-3084 URL: https://jira.jboss.org/browse/JBWS-3084 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-3.3.1, jbossws-cxf-3.3.1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 -- 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, 11 months

4
13
0 / 0

[JBoss JIRA] Updated: (JBWS-1119) Add support for fault signing and encryption

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-1119?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-1119: ---------------------------------- Fix Version/s: jbossws-native-4.0 (was: community contributions) > Add support for fault signing and encryption > -------------------------------------------- > > Key: JBWS-1119 > URL: https://issues.jboss.org/browse/JBWS-1119 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Affects Versions: jbossws-native-3.0.1 > Reporter: Jason Greene > Assignee: Alessio Soldano > Fix For: jbossws-native-4.0 > > > Add the ability to sign faults. WS-Security faults, will of course be unsigned. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3204) CLONE - JBossWS does not reuse SSL sessions

by Brad Maxwell (JIRA)

CLONE - JBossWS does not reuse SSL sessions ------------------------------------------- Key: JBWS-3204 URL: https://issues.jboss.org/browse/JBWS-3204 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: JBoss Enterprise Application Platform 5.x JBossWS 3.1.2 Reporter: Brad Maxwell Assignee: Richard Opalka Attachments: example.zip When creating a web service client and sending multiple requests over SSL to JBoss EAP the client doesn't reuse the already established connection and instead a SSL handshake takes place on every request. SSL session id is shown in ssl debug log but this is different on every request. Using Sun JAXWS libraries (remove endorsed libraries) you can see the SSL connection session id being reused on every subsequent request being made. JBossWS should reuse the already established connection and not do the expensive SSL handshake on every request. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3202) JBossWS does not reuse SSL connections

by Mustafa Musaji (JIRA)

JBossWS does not reuse SSL connections -------------------------------------- Key: JBWS-3202 URL: https://issues.jboss.org/browse/JBWS-3202 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: JBoss Enterprise Application Platform 5.x JBossWS 3.1.2 Reporter: Mustafa Musaji When creating a web service client and sending multiple requests over SSL to JBoss EAP the client doesn't reuse the already established connection and instead a SSL handshake takes place on every request. SSL session id is shown in ssl debug log but this is different on every request. Using Sun JAXWS libraries (remove endorsed libraries) you can see the SSL connection session id being reused on every subsequent request being made. JBossWS should reuse the already established connection and not do the expensive SSL handshake on every request. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2011