| Summary: | Error running webservice_wsaddressing quickstart | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jehudi Castro Sierra <jcastro> |
| Component: | Documentation, JBossESB | Assignee: | Martin Vecera <mvecera> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2 Beta 2 | CC: | mvecera |
| Target Milestone: | --- | ||
| Target Release: | 4.3 IR5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-348 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
JBoss SOA Platform ESB Standalone Server - Version 4.2.0.beta2
|
|
| Last Closed: | 2008-10-07 04:38:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
JBESB-1479 do not has the logs, but I guess that is the same issue. Link: Added: This issue depends JBESB-1479 Please remember to include a fix in value - thx. Only the productization team or the person working on the issue should set the Fix field. This is a limitation with JBossWS and will probably not get fixed until after GA. So we will have to at least document it. Affects: Added: [Documentation (Ref Guide, User Guide, etc.)] Link: Added: This issue related SOA-288 Link: Removed: This issue related SOA-288 By way of clarification. The root cause of this issue is the failure by jbossws to inject the WebserviceContext into the webservice. The warning seen on the console is 'Cannot provide WebServiceContext, since the current MessageContext does not provide a ServletRequest' and is caused by a 181 dependency on an HttpServlet. Release note: Error running webservice_wsaddressing Quickstart Running the webservice_wsaddressing quickstart currently results in an error. In the standalone version of the platform a message is produced on the console: "Cannot provide WebServiceContext, since the current MessageContext does not provide a ServletRequest". This is caused by a 181 dependency on an HttpServlet. Presently, JBoss WS does not inject the WebServiceContext into the webservice. This is due to a current limitation in JBoss WS, and will be addressed in a future update. Further Information: http://jira.jboss.com/jira/browse/SOA-348 Affects: Removed: [Documentation (Ref Guide, User Guide, etc.)] Verified in CR1 Should not have been closed. Documentation should have been a separate issue. Link: Added: This issue is related to SOA-634 Verified in 4.3 IR5 |
Date of First Response: 2008-01-23 16:25:17 project_key: SOA Ejecuting the quicktart, this step: 2. Open another command terminal window in this folder ("Window2"), type 'ant runtest'. Get this error: runtest: [java] Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException [java] at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69) [java] at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) [java] at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553) [java] at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371) [java] at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) [java] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) [java] at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) [java] at $Proxy6.addItem(Unknown Source) [java] at org.jboss.soa.esb.samples.quickstart.webservicewsa.client.WSAClient.main(WSAClient.java:48)