in reply to Client-side error Handling (SOAP,CGI)

Thanks for the replies so far. I am purposely creating the SQL/database error because I'm trying to work out error handling protocol via SOAP. I would be happy to provide more details, but I'm new to SOAP/CGI and not sure what's relevant. jhourcle, would you mind saying more about "escaping" the error message? If I just run a test case within the module itself, the following string is output:

GhrcCatSvcs.pm:GhrcCatSvcs:GhrcCatTableFields: ***Failed to prepare SQL statement: ORA-00942: table or view does not exist (DBD ERROR: error possibly near <*> indicator at char 14 in 'SELECT * FROM <*>amsu_sub WHERE 1 = 0') at GhrcCatSvcs.pm line 216.

Should I be encapsulating that in XML tags somehow?
  • Comment on Re: Client-side error Handling (SOAP,CGI)