August 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3213) xml preamble ignored for determining charset of SOAP request

by Philippe Marschall (JIRA)

xml preamble ignored for determining charset of SOAP request ------------------------------------------------------------ Key: JBWS-3213 URL: https://issues.jboss.org/browse/JBWS-3213 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Environment: Any Reporter: Philippe Marschall If a SOAP request is made with the charset specified in the XML preamble but left out in the HTTP header then JBossWS ignores the XML preamble and defaults to UTF-8. Consider for example the following request {code} POST /crm/webservice HTTP/1.0 content-type: text/xml content-length: 2240 host: example.com:8080 authorization: Basic Y3JtaTAxOnRleGFz user-agent: SAP Web Application Server (1.0;700) accept-encoding: gzip <?xml version="1.0" encoding="iso-8859-1"?>... {code} In this case JBossWS assumes UTF-8 which leads to the following exception on the first non-ASCII character: {code} 2011-02-03 16:09:39,277 3377777 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-0.0.0.0-7766-1:) SOAP request exception org.jboss.ws.core.CommonSOAPFaultException: org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence. at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:93) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:294) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:662) 2011-02-03 16:09:39,309 3377809 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] (http-0.0.0.0-7766-1:) SOAP request exception javax.xml.rpc.soap.SOAPFaultException: org.apache.xerces.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence. at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:183) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:662) {code} Looking at the code the problem seems to be that {{org.jboss.ws.core.soap.EnvelopeBuilderDOM#build(SOAPMessage, InputStream, boolean)}} always sets the encoding. In this case the {{InputSource}} should be able to determine the encoding from the preamble. The trouble seems to be that the code defaults to UTF-8 in several places earlier. {{org.jboss.ws.core.soap.EnvelopeBuilderDOM.getEncoding(SOAPMessage)}} hard codes UTF-8 as a fallback. However this can never happen because {{org.jboss.ws.core.soap.SOAPMessageImpl#SOAPMessageImpl()}} initializes as UTF-8. We will attach a full tcpdump later. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2535) Multiple security domain check is too overzealous

by Galder Zamarreno (JIRA)

Multiple security domain check is too overzealous ------------------------------------------------- Key: JBWS-2535 URL: https://jira.jboss.org/jira/browse/JBWS-2535 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assignee: Darran Lofthouse If you mix up EJB3 SLSBs without security domains and SLSBs with SecurityDomain("other"), and you add an EJB3 WS endpoint to the deployment archive, the deployment would fail with an exception similar to this: Caused by: java.lang.IllegalStateException: Multiple security domains not supported at org.jboss.wsf.container.jboss50.deployment.tomcat.SecurityHandlerEJB3.addSecurityDomain(SecurityHandlerEJB3.java:58) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.createJBossWebAppDescriptor(WebAppGenerator.java:268) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.generatWebDeployment(WebAppGenerator.java:101) at org.jboss.wsf.container.jboss50.transport.WebAppGenerator.create(WebAppGenerator.java:85) at org.jboss.wsf.container.jboss50.transport.EJBHttpTransportManager.createListener(EJBHttpTransportManager.java:78) at org.jboss.wsf.framework.deployment.HttpTransportDeploymentAspect.create(HttpTransportDeploymentAspect.java:76) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.create(DeploymentAspectManagerImpl.java:121) at org.jboss.wsf.container.jboss50.BareWSFRuntime.create(BareWSFRuntime.java:61) at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:84) at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:43) at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:112) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 18 more The validation seems to be a bit too overzealous. -- 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

12 years, 5 months

8
10
0 / 0

[JBoss JIRA] Created: (JBWS-3109) Global handler to intercept/observe inbound/outbound messages

by Gary Brown (JIRA)

Global handler to intercept/observe inbound/outbound messages ------------------------------------------------------------- Key: JBWS-3109 URL: https://jira.jboss.org/browse/JBWS-3109 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Gary Brown Although individual web services can be configured to use JAX-WS handlers to intercept messages, it would be useful to be able to define a 'global' (server wide) handler that could intercept messages inbound and outbound from any deployed web services, regardless of the web service stack in use. -- 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

12 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3287) Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name

by Alessio Soldano (JIRA)

Deployment descriptor support for declaring jbossws-config-file / jbossws-config-name ------------------------------------------------------------------------------------- Key: JBWS-3287 URL: https://issues.jboss.org/browse/JBWS-3287 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.1, jbossws-cxf-4.1 The jaxws endpoint configuration is currently declared through the @EndpointConfig annotation. The jbossws-native used to support declaring the same through context-params in the servlet web.xml. We should allow the same (perhaps even for ejb descriptor). For the jbws-cxf stack that probably implies early looking at the parameters when creating/rewriting the web.xml, as the endpoint publish (which needs those params) happens at bus startup in BusDeploymentAspect (deploy time, not runtime / when the endpoint servlet is first called) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2070) Add attachment interop endpoint for MTOM and SwaRef

by Heiko Braun (JIRA)

Add attachment interop endpoint for MTOM and SwaRef --------------------------------------------------- Key: JBWS-2070 URL: http://jira.jboss.com/jira/browse/JBWS-2070 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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

12 years, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBWS-2833) WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint"

by Morten Andersen (JIRA)

WebServiceContext#getUserPrincipal() returns null when a service is protected by "Standard WSSecurity Endpoint" --------------------------------------------------------------------------------------------------------------- Key: JBWS-2833 URL: https://jira.jboss.org/jira/browse/JBWS-2833 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: ws-security Affects Versions: jbossws-native-3.1.2 Environment: jboss-5.1.0.GA (i.e. JBoss Web Services version 3.1.2.GA) java 1.6 Reporter: Morten Andersen When exposing a webservice using the "@WebServiceProvider" annotation, and protecting it with WSSE username token the WebServiceContext#userPrincipal is not set. The WEB-INF/jboss-wsse-server.xml is configured as described here: http://www.jboss.org/community/wiki/JBossWS-WS-Securityoptions#POJO_Endpo... Although this does not really seem to be enough, as it is also required to have META-INF/standard-jaxws-endpoint-config.xml file with only the "Standard WSSecurity Endpoint" on the server to actually enforce the authentication of the username token. Attached: * wstest.war: example war - exposing one webservice (compiled from the content of server.zip) * server.zip: source for the wstest.war * client.zip: simple client for the server, sending a username token. Reproducing the problem: 1) deploy wstest.war to a jboss 5.1.0 2) open the run.sh in the client.zip, and set the JBOSS_5 to fit your installation. It the server is not listening on 8080, modify the url in the client source (WsExampleClient.java). 3) compile and run the client, by running ./run.sh 4) inspect the server log. If this says: "[INFO] Principal = null" we have the problem (expected principal = admin) Server code: * service: server.zip:src/main/java/org/example/WsExample.java * wsdl: server.zip:src/main/webapp/WEB-INF/wsdl * wsse-config: server.zip:src/main/webapp/WEB-INF/jboss-wsse-server.xml * wsse-config2: server.zip:src/main/webapp/META-INF/standard-jaxws-endpoint-config.xml It seems that "wsse-config2" is required. If this is not present, it is possible for the client to send any client credentials it want (or leave them out) and it will still get admission to the service. Other areas where this has been discussed: * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=127582&postdays=... * http://www.jboss.org/community/wiki/jbosssecuritytokenservice#comment-2075 (in relation to the same problem in the JBoss STS) -- 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

12 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-3072) The wsdl part generated for fault message is not valid

by Jim Ma (JIRA)

The wsdl part generated for fault message is not valid ------------------------------------------------------ Key: JBWS-3072 URL: https://jira.jboss.org/browse/JBWS-3072 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Jim Ma Assignee: Jim Ma -- 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

12 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-2744) Dispatch and Config Provider via System Properties and/or a Properties file

by Anil Saldhana (JIRA)

Dispatch and Config Provider via System Properties and/or a Properties file --------------------------------------------------------------------------- Key: JBWS-2744 URL: https://jira.jboss.org/jira/browse/JBWS-2744 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana The Dispatch seems to be an important JAXWS client construct. It does not provide everything that any JBossWS user needs. Hence there are chances where he may have to cast the dispatch to ConfigProvider and provide the additional settings as outlined in the forum thread. For this reason, I suggest adding a properties file on the classpath and one setting that can be done via system property. The DispatchImpl implementation needs to handle this one system prop and use the associated properties file to get the settings. -- 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

12 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBWS-3311) Make SwapableMemoryDataSource.maxMemorySize Configurable

by Kyle Lape (JIRA)

Make SwapableMemoryDataSource.maxMemorySize Configurable -------------------------------------------------------- Key: JBWS-3311 URL: https://issues.jboss.org/browse/JBWS-3311 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.1.2 Reporter: Kyle Lape Assignee: Mustafa Musaji Make the maxMemorySize configurable by a system property. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3019) Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings

by David Waters (JIRA)

Moving to jbossws-native-3.2.2.GA Stopped honering my java http proxy settings ------------------------------------------------------------------------------ Key: JBWS-3019 URL: https://jira.jboss.org/jira/browse/JBWS-3019 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Environment: jboss-5.1.0.GA, Sun java 1.6.0_14, Window XP 64bit, Intel Core2 Reporter: David Waters In order to talk to a NTLM secured webservice I go through a NTLM Http proxy (ntlmaps). I configure this proxy through a java.net.ProxySelector (ProxySelector.setDefault(aCustomProxySelector)). This was working (with issues) with the version of jbossws that ships with jboss 5.1.0GA (jbossws version 3.1.2.GA). I was required to turn off chunking so I updated to jbossws 3.2.2GA and used ChunkedEncodingFeature to disable chunking. The installation of jbossws 3.2.2 stopped the webservice calls calling my proxy selector and did not use my configured proxy. I have tried to find any way to reinstate the proxy but have been unsuccessful. -- 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

12 years, 9 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2011