Bug 777822 (SOA-348) - Error running webservice_wsaddressing quickstart
Summary: Error running webservice_wsaddressing quickstart
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-348
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation, JBossESB
Version: 4.2 Beta 2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 IR5
Assignee: Martin Vecera
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-21 18:57 UTC by Jehudi Castro Sierra
Modified: 2013-01-11 02:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 778123 0 high CLOSED Document around JBossWS WS-A issue 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-348 0 None None None Never

Internal Links: 778123

Description Jehudi Castro Sierra 2008-01-21 18:57:53 UTC
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)

Comment 1 Jehudi Castro Sierra 2008-01-21 19:00:30 UTC
JBESB-1479 do not has the logs, but I guess that is the same issue.

Comment 2 Jehudi Castro Sierra 2008-01-21 19:00:30 UTC
Link: Added: This issue depends JBESB-1479


Comment 3 Len DiMaggio 2008-01-23 21:25:17 UTC
Please remember to include a fix in value - thx.

Comment 4 Mark Little 2008-01-24 09:29:41 UTC
Only the productization team or the person working on the issue should set the Fix field.

Comment 5 Mark Little 2008-01-24 10:32:12 UTC
This is a limitation with JBossWS and will probably not get fixed until after GA. So we will have to at least document it.

Comment 6 Mark Little 2008-01-24 10:32:12 UTC
Affects: Added: [Documentation (Ref Guide, User Guide, etc.)]


Comment 7 Len DiMaggio 2008-02-04 18:05:32 UTC
Link: Added: This issue related SOA-288


Comment 8 Kevin Conner 2008-02-04 18:40:44 UTC
Link: Removed: This issue related SOA-288 


Comment 9 Kevin Conner 2008-02-04 18:43:28 UTC
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.

Comment 10 Joshua Wulf 2008-02-07 02:13:07 UTC
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

Comment 11 Joshua Wulf 2008-02-07 23:34:24 UTC
Affects: Removed: [Documentation (Ref Guide, User Guide, etc.)] 


Comment 13 Jiri Pechanec 2008-06-10 09:24:17 UTC
Verified in CR1

Comment 14 Mark Little 2008-07-18 09:46:24 UTC
Should not have been closed. Documentation should have been a separate issue.

Comment 15 Mark Little 2008-07-18 09:47:14 UTC
Link: Added: This issue is related to SOA-634


Comment 16 Jiri Pechanec 2008-10-07 04:38:10 UTC
Verified in 4.3 IR5


Note You need to log in before you can comment on or make changes to this bug.