This works fine but the fault is generic so I can't really be sure if it's because invalid username/password or some other reason. I wonder if it would be better to:
The SOAP Fault should contain your underlying CF exception (but it is a bit fiddly to unpick the data associated with the Fault).
(I tried a quick test and if you do a custom <cfthrow> none of the arguments (errorcode, detail, extendedinfo..) get passed to the soap fault.)
Right, you can only get the message back. That means that you need to handle that mapping inside your web service CFC:
<cftry>
... do stuff ...
<cfcatch type="any">
<cfthrow message="type=#cfcatch.type#;message=#cfcatch.message#; detail=#cfcatch.detail#;..." />
</cfcatch>
</cftry>
The Axis fault string begins:
AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException faultSubcode: faultString: [org.apache.axis.AxisFault : ; nested exception is: coldfusion.xml.rpc.CFCInvocationException: [coldfusion.runtime.CustomException : type=WS.EXCEPTION;message=This is the message;detail=Exception Detail;...][];
Sean A Corfield -- http://www.corfield.org/blog/
Got Mach II? -- http://www.mach-ii.com/
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
