Hi Jb, thanks for the quickly response a million dollars question. Do you remember the jira issue ? cause I'm not able to find it
Thank for help --Filippo 2014-04-01 15:33 GMT+02:00 Jean-Baptiste Onofré <[email protected]>: > Hi Filippo, > > It's not due to security, it's due to a limitation/bug in Aries JMX: it's > not possible to cleanly return something else than MBeanException (else we > may have NotSerializableException). > > If you take a look on Karaf 2.x, it was different as we don't use Aries > JMX: so we returned "clean" exception. > > I planned to change it on 3.x as soon as a fix will be available on Aries > JMX. > > Regards > JB > > > On 04/01/2014 03:30 PM, Filippo Balicchia wrote: > >> Hi, >> >> In BundlesMBeanImpl I see that exceptions are wrapper thrown new >> MBeanException using getMessage method without use of Throwable. >> >> The use e.getMessage make hard debug because the reason of the failure is >> lost. >> In this case this beavior, is desired for security reasons ? >> >> What I propose is to improve the management of the exception even using >> the >> error message displaying the error also. >> >> WDYT ? >> >> Thanks >> >> --Filippo >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
