October 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2936) Remove dependency of jbossws-native-core.jar on xerces implementation classes

by Richard Opalka (JIRA)

Remove dependency of jbossws-native-core.jar on xerces implementation classes ----------------------------------------------------------------------------- Key: JBWS-2936 URL: https://jira.jboss.org/jira/browse/JBWS-2936 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-3.3.1 -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2436) Look for eventual optimizations when scanning classes

by Alessio Soldano (JIRA)

Look for eventual optimizations when scanning classes ----------------------------------------------------- Key: JBWS-2436 URL: https://jira.jboss.org/jira/browse/JBWS-2436 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146807 -- 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, 5 months

2
11
0 / 0

[JBoss JIRA] Created: (JBWS-3077) SchemaLocation of imported schemas rewritten in WSDL do not support https

by David Boeren (JIRA)

SchemaLocation of imported schemas rewritten in WSDL do not support https ------------------------------------------------------------------------- Key: JBWS-3077 URL: https://jira.jboss.org/browse/JBWS-3077 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-2.0.1.SP2 Environment: We are using a pre-defined WSDL using the wsdlLocation annotation. However, on deployment the schema locations are rewritten as absolute URLs over http. Since we only allow https access to external clients, the concern is that they may not be able to access these xsds. We have tried transport guarantee of CONFIDENTIAL but it still does not work. Reporter: David Boeren -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2461) Request / Response Resource Optimisation

by Darran Lofthouse (JIRA)

Request / Response Resource Optimisation ---------------------------------------- Key: JBWS-2461 URL: https://jira.jboss.org/jira/browse/JBWS-2461 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.5 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.0.6 There are a few points where the management of resources can be optimised, in these places we are relying on a few techniques that are leading to potential leaks. The first area to optimise is the use of ThreadLocals for DocumentBuilders etc - these should be optimised to be better related to the request / response. A second area relates to SwapableMemoryDataSource - something is needed to clean up files not automatically deleted from killed / crashed JVMs. Secondly relying on finalize to delete the files can lead to a large number of files on disk before GC especially with large heaps. Ideally these will be better associated with the current request to be cleaned up at the end of processing. Although these are two different problems I have grouped them together as the common problem is tracking resources with the request they really belong to. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-2696) Better logging for messages that can not be parsed

by Darran Lofthouse (JIRA)

Better logging for messages that can not be parsed -------------------------------------------------- Key: JBWS-2696 URL: https://jira.jboss.org/jira/browse/JBWS-2696 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 The MessageFactoryImpl class uses for the following check for the content type of the incoming message: - if (isSoapContent(contentType) == false) { throw new SOAPException("Unsupported content type: " + contentType); } For various servers even though the incoming message is not a SOAP message the message may still contain useful information that could help diagnose the failure. Consider adding an option to still log the payload of the incoming message. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2857) Validation for Document/Literal Bare Endpoints

by Darran Lofthouse (JIRA)

Validation for Document/Literal Bare Endpoints ---------------------------------------------- Key: JBWS-2857 URL: https://jira.jboss.org/jira/browse/JBWS-2857 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.1 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.3 Section 3.6.2.2 of the JAX-WS specification describes the requirements for Document/Literal Bare deployments. JBossWS Native does not verify the requirement has been met and generates a WSDL inconsistent with the endpoint itself causing subsequent failures when the endpoint is called. The methods should be verified at deploy time. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2379) Using a custom HandlerResolver on client while using WS-Security does not add ws-security header to soap envelope

by Yousuf Haider (JIRA)

Using a custom HandlerResolver on client while using WS-Security does not add ws-security header to soap envelope ----------------------------------------------------------------------------------------------------------------- Key: JBWS-2379 URL: https://jira.jboss.org/jira/browse/JBWS-2379 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-2.0.1.SP2 Environment: JBoss4.3 JDK1.5 Reporter: Yousuf Haider I have a webservice deployed as an EJB endpoint with the correct WS-Security Configuration (using UsernameToken) My standalone java client code looks like this: ReflectorEjbWsseApi port = null; Service service = (Service) Service.create(wsdlURL, serviceQName); service.setHandlerResolver(new CustomHandlerResolver); port = service.getPort(ReflectorEjbWsseApi.class); HandlerResolver hr = new HandlerResolver(); ((BindingProvider)port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, WebServiceConstants.USERNAME); ((BindingProvider)port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, WebServiceConstants.PASSWORD); URL securityURL = new File("jboss-wsse-client.xml").toURL(); ((StubExt)port).setSecurityConfig(securityURL.toExternalForm()); ((StubExt) port).setConfigName("Standard WSSecurity Client"); ((BindingProvider)port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE); As you can see I am setting my own custom HandlerResolver. However by doing this I am somehow overriding the default HandlerChain which would have used the USERNAME_PROPERTY and PASSWORD_PROPERTY values and added the ws-security header to the soap message. When executing this code I get a SOAPFault from the server saying that the soap message does not contain a required header. javax.xml.ws.soap.SOAPFaultException: org.jboss.ws.core.CommonSOAPFaultException: This service requires <wsse:Security>, which is missing. If I don't set the handlerResolver by removing this line from my client: service.setHandlerResolver(new CustomHandlerResolver); the request goes through fine and I get a valid response. My own customhandlers do nothing but some logging activity. I should be able to use my own custom handlers with WS-Security. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2695) Setting a new config at runtime the properties are not available to RemotingConnectionImpl

by Darran Lofthouse (JIRA)

Setting a new config at runtime the properties are not available to RemotingConnectionImpl ------------------------------------------------------------------------------------------ Key: JBWS-2695 URL: https://jira.jboss.org/jira/browse/JBWS-2695 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: jbossws-native-3.2.0 Using the following to replace the configuration for the client: - ((StubExt)port).setConfigName("Custom Client Config","descriptors/jaxws-client-config.xml"); Handlers are updated as required, however the properties that are processed by RemotingConnectionImpl still use the original values. This is because the MessageContext obtains the config from the OperationMetaData as the custom config was not set when the MessageContext was created. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-3140) Process the <addressing> element in webservices.xml

by Jim Ma (JIRA)

Process the <addressing> element in webservices.xml ---------------------------------------------------- Key: JBWS-3140 URL: https://jira.jboss.org/browse/JBWS-3140 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Fix For: jbossws-cxf-3.4.0, jbossws-native-3.4.0 The <addressing> element configuration in webservices.xml does not work in both native and cxf stack. -- 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, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (JBWS-3141) Mtom configuration in webservices.xml DD doesn't work

by Jim Ma (JIRA)

Mtom configuration in webservices.xml DD doesn't work ------------------------------------------------------ Key: JBWS-3141 URL: https://jira.jboss.org/browse/JBWS-3141 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Fix For: jbossws-cxf-3.4.0 The mtom configuration in webservices.xml is not handled in cxf stack : <webservice-description> <webservice-description-name>MTOMService</webservice-description-name> <wsdl-file>WEB-INF/wsdl/MTOMwsdl</wsdl-file> <port-component> <port-component-name>MTOM</port-component-name> <wsdl-port>wsdl:MTOMPort</wsdl-port> <enable-mtom>true</enable-mtom> <protocol-binding>##SOAP11_HTTP</protocol-binding> ... </port-component> <port-component> -- 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, 5 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues October 2010