[JBoss JIRA] (JBWS-3574) SignEncryptGCMTestCase fails even if Bouncy Castle is installed
by R Searls (JIRA)
[ https://issues.jboss.org/browse/JBWS-3574?page=com.atlassian.jira.plugin.... ]
R Searls reopened JBWS-3574:
----------------------------
I'm getting the same error as described by Martin.
I'm trying to run the testsuite from repo
https://svn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite
The cmd I am using is:
mvn -Dwildfly800.home=/home/rsearls/j1/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT -Pwildfly800 integration-test
==== The ERROR message from the testsuite ====
Results :
Failed tests: testServerSideUsingConfigProperties(org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase): expected:<[1]> but was:<[# Failed tests: # Error tests: testSignEncryptUsingConfigProperties: java.lang.Exception Please check that the Bouncy Castle provider is installed.]>
Tests in error:
test221(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase): Cannot encrypt data
test222(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase): Cannot encrypt data
test223(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase): Cannot encrypt data
test224(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples22xTestCase): Cannot encrypt data
testClientSide(org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase): Please check that the Bouncy Castle provider is installed.
testClientSideUsingConfigProperties(org.jboss.test.ws.jaxws.samples.wsse.policy.basic.SignEncryptGCMTestCase): Please check that the Bouncy Castle provider is installed.
test(org.jboss.test.ws.jaxws.samples.wsse.policy.basic.AnnotatedSignEncryptTestCase): Cannot encrypt data
test2314(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase): Cannot encrypt data
test2315(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase): Cannot encrypt data
test2324(org.jboss.test.ws.jaxws.samples.wsse.policy.oasis.WSSecurityPolicyExamples23xTestCase): Cannot encrypt data
test(org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase): Cannot encrypt data
testUsingEPR(org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustTestCase): Cannot encrypt data
test(org.jboss.test.ws.jaxws.samples.wsse.policy.trust.WSTrustPicketLinkTestCase): Cannot encrypt data
testEndpointWithCustomWSSEAndWSA(org.jboss.test.ws.jaxws.cxf.jbws3648.PolicyAttachmentTestCase): Cannot encrypt data
Tests run: 176, Failures: 1, Errors: 14, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Web Services - Stack CXF Testsuite .......... SUCCESS [4.771s]
[INFO] JBoss Web Services - Stack CXF Test utils ......... SUCCESS [1.652s]
[INFO] JBoss Web Services - Stack CXF Specific Tests ..... FAILURE [1:20.827s]
[INFO] JBoss Web Services - Stack Agnostic Tests ......... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:27.543s
[INFO] Finished at: Fri Jan 10 11:02:15 EST 2014
[INFO] Final Memory: 32M/401M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (integration-tests) on project jbossws-cxf-specific-tests: There are test failures.
[ERROR]
[ERROR] Please refer to /home/rsearls/j1/jbossws/trunk/modules/testsuite/cxf-tests/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :jbossws-cxf-specific-tests
1152 >
===== WildFly 8.0.0 reports the following WARNING and stacktrace =====
11:01:51,192 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "jaxws-samples-schemavalidation.war" (runtime-name: "jaxws-samples-schemavalidation.war")
11:01:51,236 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-7) JBWS024061: Adding service endpoint metadata: id=ValidatingHelloService
address=http://localhost:8080/jaxws-samples-schemavalidation/validatingHello
implementor=org.jboss.test.ws.jaxws.samples.schemavalidation.ValidatingHelloImpl
serviceName={http://jboss.org/schemavalidation}HelloService
portName={http://jboss.org/schemavalidation}ValidatingHelloPort
annotationWsdlLocation=WEB-INF/wsdl/hello.wsdl
wsdlLocationOverride=null
mtomEnabled=false
11:01:51,236 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-7) JBWS024061: Adding service endpoint metadata: id=HelloService
address=http://localhost:8080/jaxws-samples-schemavalidation/hello
implementor=org.jboss.test.ws.jaxws.samples.schemavalidation.HelloImpl
serviceName={http://jboss.org/schemavalidation}HelloService
portName={http://jboss.org/schemavalidation}HelloPort
annotationWsdlLocation=WEB-INF/wsdl/hello.wsdl
wsdlLocationOverride=null
mtomEnabled=false
11:01:51,247 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://jboss.org/schemavalidation}HelloService from WSDL: WEB-INF/wsdl/hello.wsdl
11:01:51,255 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/jaxws-samples-schemavalidation/validatingHello
11:01:51,258 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/rsearls/j1/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT/standalone/data/wsdl/jaxws-samples-schemavalidation.war/hello.wsdl
11:01:51,258 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-7) Creating Service {http://jboss.org/schemavalidation}HelloService from WSDL: WEB-INF/wsdl/hello.wsdl
11:01:51,260 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/jaxws-samples-schemavalidation/hello
11:01:51,263 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/rsearls/j1/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT/standalone/data/wsdl/jaxws-samples-schemavalidation.war/hello.wsdl
11:01:51,264 INFO [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.endpoint."jaxws-samples-schemavalidation.war".ValidatingHelloService
11:01:51,264 INFO [org.jboss.as.webservices] (MSC service thread 1-7) JBAS015539: Starting service jboss.ws.endpoint."jaxws-samples-schemavalidation.war".HelloService
11:01:51,271 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Register web context: /jaxws-samples-schemavalidation
11:01:51,366 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "jaxws-samples-schemavalidation.war" (runtime-name : "jaxws-samples-schemavalidation.war")
11:01:51,370 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTPS listener jbws-test-https-listener listening on /127.0.0.1:8443
11:01:51,473 INFO [stdout] (default task-6) ValidatingHello: JBoss
11:01:51,542 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/rsearls/j1/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT/standalone/data/content/41/bbe877b22ae49874f4874dfe86421fc2db1eec/content
11:01:51,545 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "jaxws-samples-wsse-policy-oasis-21x.war" (runtime-name: "jaxws-samples-wsse-policy-oasis-21x.war")
11:01:51,561 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (default task-4) Interceptor for {http://jboss.org/schemavalidation}HelloService#{http://jboss.org/schemavalidation}helloRequest has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unmarshalling Error: cvc-enumeration-valid: Value 'number' is not facet-valid with respect to enumeration '[JBoss, CXF]'. It must be a value from the enumeration.
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:881)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:702)
at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:157)
at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:192) [cxf-api-2.7.7.jar:2.7.7]
at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272) [cxf-api-2.7.7.jar:2.7.7]
at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121) [cxf-api-2.7.7.jar:2.7.7]
at org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(AbstractHTTPDestination.java:239)
at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:92)
at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:143)
at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:286)
at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.2.2.Final.jar:2.2.2.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:70)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:67) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:654) [undertow-core-1.0.0.Beta30.jar:1.0.0.Beta30]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
Caused by: javax.xml.bind.UnmarshalException
- with linked exception:
[org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 150; cvc-enumeration-valid: Value 'number' is not facet-valid with respect to enumeration '[JBoss, CXF]'. It must be a value from the enumeration.]
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:435)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:372)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:349)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.doUnmarshal(JAXBEncoderDecoder.java:842)
at org.apache.cxf.jaxb.JAXBEncoderDecoder.access$100(JAXBEncoderDecoder.java:101)
at org.apache.cxf.jaxb.JAXBEncoderDecoder$2.run(JAXBEncoderDecoder.java:870)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25]
at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:868)
... 39 more
Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 150; cvc-enumeration-valid: Value 'number' is not facet-valid with respect to enumeration '[JBoss, CXF]'. It must be a value from the enumeration.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(Unknown Source)
at org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.endElement(Unknown Source)
at com.sun.xml.bind.v2.runtime.unmarshaller.ValidatingUnmarshaller.endElement(ValidatingUnmarshaller.java:106)
at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.handleEndElement(StAXStreamConnector.java:221)
at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:185)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:370)
... 45 more
11:01:51,579 INFO [stdout] (default task-20) Hello: JBoss
11:01:51,583 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment jaxws-samples-wsse-policy-oasis-21x.war
=== bouncycastle is installed in the server here ====
---
/home/rsearls/j1/wildfly/build/target/wildfly-8.0.0.Final-SNAPSHOT
./modules/system/layers/base/org/bouncycastle/main/bcmail-jdk16-1.46.jar
./modules/system/layers/base/org/bouncycastle/main/bcprov-jdk16-1.46.jar
==== My run env is as follows ====
1155 > uname -a
Linux dhcp-185-161.bos.redhat.com 3.11.10-100.fc18.x86_64 #1 SMP Mon Dec 2 20:28:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
1158 > mvn -version
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-27 22:15:32-0400)
Maven home: /home/rsearls/d5/apache-maven-3.1.0
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_25/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.11.10-100.fc18.x86_64", arch: "amd64", family: "unix"
1159 > svn info
Path: .
Working Copy Root Path: /home/rsearls/j1/jbossws/trunk
URL: https://svn.jboss.org/repos/jbossws/stack/cxf/trunk/modules/testsuite
Repository Root: https://svn.jboss.org/repos/jbossws
Repository UUID: 50344849-fb0f-0410-a53f-a94597aac05c
Revision: 18225
Node Kind: directory
Schedule: normal
Last Changed Author: asoldano
Last Changed Rev: 18197
Last Changed Date: 2013-12-17 11:03:49 -0500 (Tue, 17 Dec 2013)
1139 > g remote -v
upstream https://github.com/wildfly/wildfly.git (fetch)
Branched from upstream/master
> SignEncryptGCMTestCase fails even if Bouncy Castle is installed
> ---------------------------------------------------------------
>
> Key: JBWS-3574
> URL: https://issues.jboss.org/browse/JBWS-3574
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-3.1.2
> Environment: JBoss Web Services - Stack CXF 3.1.2.SP12, Oracle JDK 1.7.0_09 with Bouncy Castle installed (both bcprov-ext-jdk15on-147.jar and bcprov-jdk15on-147.jar), RHEL 5 x86
> Reporter: Martin Vecera
> Assignee: Richard Opalka
> Attachments: TEST-org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.xml
>
>
> I run WS-CXF integration test suite against SOA-P 5.3.1 and I faces issues with security tests due to missing Bouncy Castle installation. After installing it, there is still a test that fails:
> java.lang.Exception: Please check that the Bouncy Castle provider is installed.
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:65)
> Caused by: javax.xml.ws.soap.SOAPFaultException: Cannot encrypt data
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy38.sayHello(Unknown Source)
> at org.jboss.test.ws.jaxws.samples.wssePolicy.SignEncryptGCMTestCase.test(SignEncryptGCMTestCase.java:61)
> ... 30 more
> Caused by: org.apache.cxf.ws.policy.PolicyException: Cannot encrypt data
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AbstractBindingBuilder.policyNotAsserted(AbstractBindingBuilder.java:283)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doEncryption(AsymmetricBindingHandler.java:319)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.doSignBeforeEncrypt(AsymmetricBindingHandler.java:141)
> at org.apache.cxf.ws.security.wss4j.policyhandlers.AsymmetricBindingHandler.handleBinding(AsymmetricBindingHandler.java:90)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:139)
> at org.apache.cxf.ws.security.wss4j.PolicyBasedWSS4JOutInterceptor$PolicyBasedWSS4JOutInterceptorInternal.handleMessage(PolicyBasedWSS4JOutInterceptor.java:77)
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> ... 32 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3530:
----------------------------------
Assignee: (was: Alessio Soldano)
> Add some hints to the code generated by cxf using wsconsume to tune generated code before use
> ---------------------------------------------------------------------------------------------
>
> Key: JBWS-3530
> URL: https://issues.jboss.org/browse/JBWS-3530
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.0.2
> Environment: JBossWS CXF
> Reporter: Mustafa Musaji
> Priority: Trivial
> Labels: webservices
> Fix For: jbossws-cxf-4.4
>
>
> The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized.
> {code:title=WSService.java|borderStyle=solid}
> static {
> URL url = null;
> try {
> url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> } catch (MalformedURLException e) {
> java.util.logging.Logger.getLogger(WSProviderService.class.getName())
> .log(java.util.logging.Level.INFO,
> "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> }
> WSDL_LOCATION = url;
> }
> {code}
> This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3530:
----------------------------------
Fix Version/s: jbossws-cxf-4.4
> Add some hints to the code generated by cxf using wsconsume to tune generated code before use
> ---------------------------------------------------------------------------------------------
>
> Key: JBWS-3530
> URL: https://issues.jboss.org/browse/JBWS-3530
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.0.2
> Environment: JBossWS CXF
> Reporter: Mustafa Musaji
> Assignee: Alessio Soldano
> Priority: Trivial
> Labels: webservices
> Fix For: jbossws-cxf-4.4
>
>
> The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized.
> {code:title=WSService.java|borderStyle=solid}
> static {
> URL url = null;
> try {
> url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> } catch (MalformedURLException e) {
> java.util.logging.Logger.getLogger(WSProviderService.class.getName())
> .log(java.util.logging.Level.INFO,
> "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> }
> WSDL_LOCATION = url;
> }
> {code}
> This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3530) Add some hints to the code generated by cxf using wsconsume to tune generated code before use
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3530?page=com.atlassian.jira.plugin.... ]
Alessio Soldano commented on JBWS-3530:
---------------------------------------
We might need an option in cxf codebase for doing this.
> Add some hints to the code generated by cxf using wsconsume to tune generated code before use
> ---------------------------------------------------------------------------------------------
>
> Key: JBWS-3530
> URL: https://issues.jboss.org/browse/JBWS-3530
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.0.2
> Environment: JBossWS CXF
> Reporter: Mustafa Musaji
> Priority: Trivial
> Labels: webservices
> Fix For: jbossws-cxf-4.4
>
>
> The generated code when using wsconsume is not really meant for use in production environment with the statically initialized wsdlLocation and the error that will be logged when this the Service object is first initialized.
> {code:title=WSService.java|borderStyle=solid}
> static {
> URL url = null;
> try {
> url = new URL("file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> } catch (MalformedURLException e) {
> java.util.logging.Logger.getLogger(WSProviderService.class.getName())
> .log(java.util.logging.Level.INFO,
> "Can not initialize the default wsdl from {0}", "file:/directory/to/wsdl/WSTestEJB/ejbModule/META-INF/WSProvider.wsdl");
> }
> WSDL_LOCATION = url;
> }
> {code}
> This is a request to amend the log level to "DEBUG" and/or have wsconsume create a hint of sorts to tune this class before use in a container.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3741) WebService doesn't support "//"
by Alessio Soldano (JIRA)
[ https://issues.jboss.org/browse/JBWS-3741?page=com.atlassian.jira.plugin.... ]
Alessio Soldano updated JBWS-3741:
----------------------------------
Fix Version/s: jbossws-cxf-4.3
> WebService doesn't support "//"
> --------------------------------
>
> Key: JBWS-3741
> URL: https://issues.jboss.org/browse/JBWS-3741
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-cxf
> Affects Versions: jbossws-cxf-4.1.3
> Reporter: Thomas Szadel
> Priority: Minor
> Fix For: jbossws-cxf-4.3
>
>
> The WebService part of Jboss eap 6 doesn't support double slash ('//') in URI (although JBoss 5 supports it and the Web connector also supports it).
> That's to say, those 3 urls should represent the same one :
> * http://localhost:8080/ws/myWs?wsdl
> * http://localhost:8080/ws//myWs?wsdl
> * http://localhost:8080//ws/myWs?wsdl
> BUT only the first one is accepted by JBoss. The others raise that stack trace:
> javax.servlet.ServletException: JBWS024029: Cannot obtain destination for /ws//myWs
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:170)
> org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:87)
> org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:156)
> org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:225)
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:150)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
> org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
> AND if I call the following URL, it works : http://localhost:8080/./ws/myWs?wsdl
> IMHO, the method org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination should use a "canonical path" before testing the equality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3750) Add ability to rewrite path in WSDL URL references
by Kyle Lape (JIRA)
Kyle Lape created JBWS-3750:
-------------------------------
Summary: Add ability to rewrite path in WSDL URL references
Key: JBWS-3750
URL: https://issues.jboss.org/browse/JBWS-3750
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: Kyle Lape
Currently JBossWS/CXF have the ability to configure a custom host and/or port to use when populating the soap:address and schemaLocation items in a WSDL. This request is to add the ability to configure a custom URL path in addition to the host and port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months
[JBoss JIRA] (JBWS-3749) update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0
by R Searls (JIRA)
R Searls created JBWS-3749:
------------------------------
Summary: update build-testsuite.xml to reflect new location of netty module in wildfly 8.0.0
Key: JBWS-3749
URL: https://issues.jboss.org/browse/JBWS-3749
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-cxf
Reporter: R Searls
Assignee: R Searls
The module location of netty has changed wildfly 8.0.0. It was located in
${jboss.home}/modules/system/layers/base/org/jboss/netty/main/
its now located in
${jboss.home}/modules/system/layers/base/io/netty/main/
File build-testsuite.xml needs to be updated to reflect this so testsuite will run.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 3 months