[JBoss JIRA] Created: (JBWS-3253) JBossWS does not decode Nonce
by Brad Maxwell (JIRA)
JBossWS does not decode Nonce
-----------------------------
Key: JBWS-3253
URL: https://issues.jboss.org/browse/JBWS-3253
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ws-security
Affects Versions: jbossws-native-3.1.2, jbossws-native-3.2.0, jbossws-native-3.2.2
Environment: JDK 6
JBoss 5.1.0 jdk 6
Windows XP
Reporter: Brad Maxwell
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.4.0.CR1
Attachments: UsernameTokenCallback.java
I am filing this bug after discussing http://community.jboss.org/message/540669
Nonce is not decoded when encoding type is Base64.
UsernameToken has this piece of code:
String encodingType = elem.getAttribute("EncodingType");
if (encodingType != null && encodingType.length() > 0 && !Constants.BASE64_ENCODING_TYPE.equalsIgnoreCase(encodingType))
throw new WSSecurityException("Unsupported nonce encoding type: " + encodingType);
encodingType is not used anywhere else.
In UsernameTokenCallback.java there is the need to decode nonce, so, something like:
String nonce = (String)info.getInfo(NONCE);
if (nonce != null) {
try {
digest.update(new BASE64Decoder().decodeBuffer(nonce));
} catch (IOException e) {
// ignore exceptions
}
}
need to be added to UsernameTokenCallback.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3243) Apache WSSecurity relies on TCCL when lookuping it's providers
by Richard Opalka (JIRA)
Apache WSSecurity relies on TCCL when lookuping it's providers
--------------------------------------------------------------
Key: JBWS-3243
URL: https://issues.jboss.org/browse/JBWS-3243
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
10:25:08,293 ERROR [org.apache.xml.security.Init] (http-8080-1) Bad: : java.lang.RuntimeException: java.lang.ClassNotFoundException: org/apache/xml/security/transforms/implementations/TransformBase64Decode
at org.apache.xml.security.transforms.Transform.register(Unknown Source)
at org.apache.xml.security.Init.init(Unknown Source)
at org.jboss.ws.extensions.security.SecurityDecoder.<init>(SecurityDecoder.java:80) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeHeader(WSSecurityDispatcher.java:127) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:98) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) [jbossws-common.jar:2.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87) [jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: java.lang.ClassNotFoundException: org/apache/xml/security/transforms/implementations/TransformBase64Decode
at java.lang.Class.forName0(Native Method) [:1.6.0_20]
at java.lang.Class.forName(Class.java:264) [:1.6.0_20]
... 31 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3247) Endpoint TCCL is not updated after the enclosing deployment is redployed
by Magesh Bojan (JIRA)
Endpoint TCCL is not updated after the enclosing deployment is redployed
------------------------------------------------------------------------
Key: JBWS-3247
URL: https://issues.jboss.org/browse/JBWS-3247
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-3.4.1
Environment: AS 6.0.0.Final
Reporter: Magesh Bojan
Assignee: Magesh Bojan
Fix For: jbossws-cxf-4.0
Consider an Endpoint class bundled with a war deployment. This Endpoint is created (using Endpoint.publish) and stopped within the war's lifecyle. However the TCCL attached to this endpoint instance (irrespective of redeployment) is always that of the first deployment's TCCL.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3242) Servlet base test throws IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found
by Richard Opalka (JIRA)
Servlet base test throws IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found
----------------------------------------------------------------------------------------------------------
Key: JBWS-3242
URL: https://issues.jboss.org/browse/JBWS-3242
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
16:12:35,130 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jaxws-jbws3223-servlet].[TestService]] (http-8080-5) Servlet.service() for servlet TestService threw exception: javax.xml.ws.WebServiceException: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found
at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:120)
at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:128)
at javax.xml.ws.Service.<init>(Service.java:57) [jboss-jaxws-api_2.2_spec-2.0.0.Alpha1.jar:2.0.0.Alpha1]
at javax.xml.ws.Service.create(Service.java:687) [jboss-jaxws-api_2.2_spec-2.0.0.Alpha1.jar:2.0.0.Alpha1]
at org.jboss.test.ws.jaxws.jbws3223.Client.run(Client.java:48) [classes:]
at org.jboss.test.ws.jaxws.jbws3223.TestServlet.doGet(TestServlet.java:46) [classes:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: java.lang.IllegalArgumentException: Resource META-INF/jbossws-entities.properties not found
at org.jboss.ws.core.utils.JBossWSEntityResolver$1.run(JBossWSEntityResolver.java:109)
at org.jboss.ws.core.utils.JBossWSEntityResolver$1.run(JBossWSEntityResolver.java:103)
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_20]
at org.jboss.ws.core.utils.JBossWSEntityResolver.loadEntitiesMappingFromClasspath(JBossWSEntityResolver.java:102)
at org.jboss.ws.core.utils.JBossWSEntityResolver.<init>(JBossWSEntityResolver.java:83)
at org.jboss.ws.core.utils.JBossWSEntityResolver.<init>(JBossWSEntityResolver.java:61)
at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:105)
at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:96)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:75)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:154)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.<init>(ServiceDelegateImpl.java:125)
at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:114)
... 19 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3241) NPE in ServerHandler.handleInbound()
by Richard Opalka (JIRA)
NPE in ServerHandler.handleInbound()
------------------------------------
Key: JBWS-3241
URL: https://issues.jboss.org/browse/JBWS-3241
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
16:03:16,817 ERROR [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] (http-8080-2) Exception during handler processing: java.lang.NullPointerException
at org.jboss.test.ws.jaxws.samples.addressing.ServerHandler.handleInbound(ServerHandler.java:55) [classes:]
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) [jbossws-common.jar:2.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:204) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87) [jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3239) Fix SPI TCCL issue for servlet deployments trying to do Endpoint.publish()
by Richard Opalka (JIRA)
Fix SPI TCCL issue for servlet deployments trying to do Endpoint.publish()
--------------------------------------------------------------------------
Key: JBWS-3239
URL: https://issues.jboss.org/browse/JBWS-3239
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
15:09:44,291 ERROR [org.jboss.wsf.common.invocation.InvocationHandlerJAXWS] (http-8080-2) Method invocation failed with exception: null: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_20]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_20]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_20]
at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_20]
at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:102) [jbossws-common.jar:2.0.0-SNAPSHOT]
at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:241) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87) [jbossws-common.jar:2.0.0-SNAPSHOT]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta4.jar:7.0.0.Alpha2-SNAPSHOT]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: java.lang.ClassCastException: org.jboss.wsf.framework.deployment.DefaultDeployment cannot be cast to org.jboss.wsf.spi.deployment.ArchiveDeployment
at org.jboss.ws.core.jaxws.spi.http.NettyHttpServerAdapter.newDeployment(NettyHttpServerAdapter.java:157) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.spi.http.NettyHttpServerAdapter.publish(NettyHttpServerAdapter.java:102) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.spi.EndpointImpl.publish(EndpointImpl.java:165) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.ws.core.jaxws.spi.EndpointImpl.publish(EndpointImpl.java:132) [jbossws-native-core.jar:4.0.0-SNAPSHOT]
at org.jboss.test.ws.jaxws.endpoint.WSClientEndpointBean.echo(WSClientEndpointBean.java:46) [classes:]
... 24 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] Created: (JBWS-3238) Rewrite jaxws tools tests to run in fork mode
by Alessio Soldano (JIRA)
Rewrite jaxws tools tests to run in fork mode
---------------------------------------------
Key: JBWS-3238
URL: https://issues.jboss.org/browse/JBWS-3238
Project: JBoss Web Services
Issue Type: 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
Currently the jaxws tools are run loading the WSConsumerPlugin/WSProviderPlugin classes in a separate classloader (that sees the same libs as those found in the surefire classpath). After the latest changes on JBoss Modules to deal with setting proper JAXP factories, and considering Apache CXF also performs some hacks when loading LogUtils (which in turn uses JAXP stuff), it has became evident that we can't go on trying to isolate the tools run simply by changing the classloader. We need to run each tests there in a new jvm.
A way of achieving that is probably to use the JUnit test runner http://junit.sourceforge.net/junit3.8.1/javadoc/junit/textui/TestRunner.html similarly to what we already do in WSRunClientTestCase::test()
The aim would be to run something like what follows from the PluginBase::dispatch():
java -cp modified-classpath junit.textui.TestRunner org.jboss.test.ws.jaxws.smoke.tools.WSProviderPlugin
except we then need just one call for each plugin to avoid running tests multiple times.
Another solution is adding a new execution to the surefire plugin, having the forkMode option set to "pertest".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months