January 2009 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2064) JSON content-type handling

by Thomas Diesler (JIRA)

JSON content-type handling -------------------------- Key: JBWS-2064 URL: http://jira.jboss.com/jira/browse/JBWS-2064 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Diesler Fix For: jbossws-native-2.0.5 -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2478) Investigate why jaxws/samples/wsse CXF tests are failing

by Richard Opalka (JIRA)

Investigate why jaxws/samples/wsse CXF tests are failing -------------------------------------------------------- Key: JBWS-2478 URL: https://jira.jboss.org/jira/browse/JBWS-2478 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-cxf-3.0.6 The wsse CXF security tests stopped working after upgrade to CXF 2.1.3. The reason of regression needs to be investigated. [/home/opalka][/home/opalka/svn/jbossws/stack/cxf/trunk]>mvn -Ptestsuite,hudson,jboss500 -Dtest=**/jaxws/samples/wsse/*TestCase -Dnoprepare test Running org.jboss.test.ws.jaxws.samples.wsse.SignTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.709 sec <<< FAILURE! Running org.jboss.test.ws.jaxws.samples.wsse.SignEncryptTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.678 sec <<< FAILURE! Running org.jboss.test.ws.jaxws.samples.wsse.UsernameTestCase Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.806 sec <<< FAILURE! Results : Tests in error: test(org.jboss.test.ws.jaxws.samples.wsse.SignTestCase) test(org.jboss.test.ws.jaxws.samples.wsse.SignEncryptTestCase) test(org.jboss.test.ws.jaxws.samples.wsse.UsernameTestCase) Tests run: 4, Failures: 0, Errors: 3, Skipped: 0 The exception on server side is: org.apache.ws.security.WSSecurityException: An error was discovered processing the <wsse:Security> header at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:237) at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:65) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78) at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:92) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:285) at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:154) at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) 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.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:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 15:44:45,330 INFO [PhaseInterceptorChain] Interceptor has thrown exception, unwinding now org.apache.cxf.binding.soap.SoapFault: An error was discovered processing the <wsse:Security> header at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.createSoapFault(WSS4JInInterceptor.java:405) at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:256) at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:65) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220) at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78) at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:92) at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:285) at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:154) at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) 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.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:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.ws.security.WSSecurityException: An error was discovered processing the <wsse:Security> header at org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JInInterceptor.java:237) ... 29 more -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2419) MTOM/XOP message use always "text/xml" for start-info regardless of 'type' parameter of root part!

by Franz Willer (JIRA)

MTOM/XOP message use always "text/xml" for start-info regardless of 'type' parameter of root part! -------------------------------------------------------------------------------------------------- Key: JBWS-2419 URL: https://jira.jboss.org/jira/browse/JBWS-2419 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Franz Willer MultipartRelatedXOPEncoder use MimeConstants.START_INFO_XOP ("text/xml" = TYPE_SOAP11) to set 'start-info' parameter. But in "XML-binary Optimized Packaging" (http://www.w3.org/TR/xop10) "4.1 MIME Multipart/Related XOP Packages" is stated that start-info must contain the value of 'type' parameter from root part: 4.1 MIME Multipart/Related XOP Packages .. The root MIME part is the root part of the XOP package, MUST be a serialization of the XOP Infoset using any W3C recommendation-level version of XML (e.g., [Extensible Markup Language (XML) 1.0 (Third Edition)], [Extensible Markup Language (XML) 1.1]), and MUST be identified with a media type of "application/xop+xml" (as defined below). The "start-info" parameter of the package's media type MUST contain the content type associated with the content's XML serialization. (i.e. it will contain the same value as the "type" parameter of the root part). .. One effect of this is, that AXIS2 clients will throw an exception because they check if the SOAP Envelope namespace (SOAP11 or SOAP12) is conform to the transport Content-Type (text/xml or application/soap+xml). -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2417) Update to more recent CXF components

by Alessio Soldano (JIRA)

Update to more recent CXF components ------------------------------------ Key: JBWS-2417 URL: https://jira.jboss.org/jira/browse/JBWS-2417 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-cxf-3.0.6 We're currently using cxf artifact of version 2.1. CXF 2.1.3 is out, we should evaluate upgrading to that version as some issues have been solved in the latest releases. -- 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

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2118) context-root in jboss.xml is ignored

by Thomas Diesler (JIRA)

context-root in jboss.xml is ignored ------------------------------------ Key: JBWS-2118 URL: http://jira.jboss.com/jira/browse/JBWS-2118 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native, jbossws-jaxrpc Affects Versions: jbossws-2.0.1 Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: jbossws-native-2.0.3 I want to override the default context root for my Web Services. So in my jboss.xml for (myEjb.jar) I have [QUOTE] <context-root>/webservices</context-root> [/QUOTE] inside the jboss->webservices node. But this doesn't seem to be working, the WSDLs are published at http://host/myApp-myEjb/ -- 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

15 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-1774) Provide a tools implementation for CXF (WSContractProvider and WSContractConsumer)

by Heiko Braun (JIRA)

Provide a tools implementation for CXF (WSContractProvider and WSContractConsumer) ---------------------------------------------------------------------------------- Key: JBWS-1774 URL: http://jira.jboss.com/jira/browse/JBWS-1774 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: integration-cxf 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

15 years, 11 months

4
21
0 / 0

[JBoss JIRA] Created: (JBWS-2377) jbossws-deploy.conf in 'all' configuration links libraries in 'default' conf

by Alessio Soldano (JIRA)

jbossws-deploy.conf in 'all' configuration links libraries in 'default' conf ---------------------------------------------------------------------------- Key: JBWS-2377 URL: https://jira.jboss.org/jira/browse/JBWS-2377 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Alessio Soldano The jboss-4.2.3.GA binary comes with jbossws-deploy.conf in 'all' configuration (server/all/deploy/jbossws.sar/jbossws-deploy.conf) with the following contents: bin/wsconsume.bat bin/wsconsume.sh bin/wsprovide.bat bin/wsprovide.sh bin/wsrunclient.bat bin/wsrunclient.sh bin/wstools.bat bin/wstools.sh client/FastInfoset.jar client/jaxb-api.jar client/jaxb-impl.jar client/jaxb-xjc.jar client/jaxws-rt.jar client/jaxws-tools.jar client/jboss-jaxrpc.jar client/jboss-jaxws-ext.jar client/jboss-jaxws.jar client/jboss-saaj.jar client/jbossws-client.jar client/jbossws-common.jar client/jbossws-framework.jar client/jbossws-spi.jar client/jettison.jar client/policy.jar client/stax-api.jar client/stax-ex.jar client/streambuffer.jar client/wsdl4j.jar client/wstx.jar lib/jaxb-api.jar lib/jaxb-impl.jar server/default/lib/jboss-jaxrpc.jar server/default/lib/jboss-jaxws-ext.jar server/default/lib/jboss-jaxws.jar server/default/lib/jboss-saaj.jar server/default/lib/jbossws-common.jar server/default/lib/jbossws-framework.jar server/default/lib/jbossws-spi.jar Please note it refers the default configuration. This can lead to broken installation of JBossWS-Metro/CXF over the 'all' configuration. Need to check every other containers and understand why this happened / how to fix. -- 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

15 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2223) wsconsume for cxf build

by Thomas Diesler (JIRA)

wsconsume for cxf build ----------------------- Key: JBWS-2223 URL: http://jira.jboss.com/jira/browse/JBWS-2223 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Thomas Diesler -- 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

15 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2263) Fix container integration

by Alessio Soldano (JIRA)

Fix container integration ------------------------- Key: JBWS-2263 URL: https://jira.jboss.org/jira/browse/JBWS-2263 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alessio Soldano Assignee: Alessio Soldano -- 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

15 years, 11 months

1
6
0 / 0

[JBoss JIRA] Created: (JBWS-1967) Get rid of web.xml rewrite

by Heiko Braun (JIRA)

Get rid of web.xml rewrite -------------------------- Key: JBWS-1967 URL: http://jira.jboss.com/jira/browse/JBWS-1967 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun Fix For: jbossws-native-2.0.4 Scott wrote: The tomcat layer is being driven by the WebMetaData/JBossWebMetaData now, so any modification by the ws deployers should be done as input into a deployer like MergedJBossMetaDataDeployer does for the ejb metadata. I'd like to get this cleaned up for jbossas 5.0.0.CR1 when the war deployer is cleaned up. -- 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

15 years, 11 months

4
15
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2009