[ http://issues.apache.org/jira/browse/BEEHIVE-805?page=all ]
Eddie O'Neil resolved BEEHIVE-805:
----------------------------------
Fix Version: 1.1
Resolution: Fixed
Assign To: (was: daryoush mehrtash)
Fixed in SVN 345908 -- a reasonable error message is now printed when accessing
a JWS that doesn't exist in the presence of WSM.
> NullPointerException Fault is generated when calling a non-existant jws
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-805
> URL: http://issues.apache.org/jira/browse/BEEHIVE-805
> Project: Beehive
> Type: Bug
> Components: Web Services (181)
> Reporter: daryoush mehrtash
> Fix For: 1.1
>
> To reproduce the problem isntall a jws webapplication, eg.
> wsm-samples-addressbookEnhanced. try to get the wsdl of a nonexisting JWS
> in the installed application:
> http://localhost:8080/EnhancedAddressBookWS/xxxxxx.jws?wsdl
> You get a message like:
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
> faultSubcode:
> faultString: java.lang.NullPointerException
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:DMEHRTAS02
> The problem is that the
> AnnotatedWebServiceDeploymentHandler.getWebServiceClass doesn't generate the
> a descriptive fault. Here is what it does now (around like242)
> if(null == clazz)
> if(logger.isDebugEnabled())
> logger.debug("failed to load web service class: " +
> className);
> return clazz;
> This should be enhanced to actaully send a Fault back to the client.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
