[ http://issues.apache.org/jira/browse/CXF-185?page=comments#action_12448355 ] tli commented on CXF-185: -------------------------
I think it's better that we allow user to config this item at 2 level, one is on bus level, the other is on service level. > handling stack trace in fault > ----------------------------- > > Key: CXF-185 > URL: http://issues.apache.org/jira/browse/CXF-185 > Project: CXF > Issue Type: Bug > Reporter: Bozhong Lin > Assigned To: tli > > There is a discussion in mailing thread related to how to handle stack trace > in fault, solution has been suggested, so I created a jira issue to track: > Glynn, Eoghan wrote: > > > > > >> -----Original Message----- > >> From: Dan Diephouse [mailto:[EMAIL PROTECTED] Sent: 20 October 2006 18:06 > >> To: [email protected] > >> Subject: Re: stacktrace in fault? > >> > >> James Mao wrote: > >> > >> > >>> I'm thinking of adding a getStackTrace()/setStackTrace into Fault I saw > >>> in XML binding we just set the stacktrace into the message, i don't think > >>> that is correct way. > >>> Any idea? > >>> > >>> -james. > >>> > >>> > >>> > >> I don't think we should be sending the stack trace along with the fault. > >> We should log the stack trace on the server side and send information to > >> the client that there was some error processing, but shouldn't necessarily > >> tell them all the details. > >> > >> - Dan > >> > > > > I'd disagree. In certain circumstances, I think sending on the wire the > > stack trace of the exception that gave rise to the fault would actually > > be very useful for debugging and problem reporting. It could lead to > > much quicker resolution of issues reported by client-side developers, as > > opposed to trawling thru' (potentially very large) server-side logs. > > > > I'd see this as analogous to the CORBA ExceptionDetailMessage service > > context, which is often used by Java ORBs to marshall the offending > > stack trace into the exception reply. As the content of the stack trace > > may be deemed "sensitive", say in the case of a secure server, this > > facility can usually be turned off via configuration. > > > > /Eoghan > > > > > I would be happy with a configuration switch :-) > - Dan -- 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
