Not sure I understand. I'm catching all exceptions in the Hessian service implementation method, and then throwing a simple, simplified one. But it seems that Hessian wraps that in something with a ton of detail. To be sure, my simplified exception resulted in a much smaller return payload (4k vs 24k), but it's still way too much, not to mention to revealing of what the server is doing.
On Nov 23, 2013, at 23:15 , Jeff Schnitzer <j...@infohazard.org> wrote: > Are you using any kind of DI framework? Apply an interceptor that catches and > throws your stripped down exception. > > Jeff > > On Nov 24, 2013 6:13 AM, "Rick Mann" <rm...@latencyzero.com> wrote: > If my server-side Hessian method throws an exception, what gets sent back to > my client is very verbose, complete with a stack trace. > > Is there any way to prevent Hessian from doing this? I'd like to throw a > simple, custom exception, and have only the data contained in that exception > get sent back to the client; not the entire call stack that led to it. > > -- > Rick > > > > > _______________________________________________ > hessian-interest mailing list > hessian-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/hessian-interest > > _______________________________________________ > hessian-interest mailing list > hessian-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/hessian-interest -- Rick
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ hessian-interest mailing list hessian-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/hessian-interest
