I totally argree with Thomas, that a custom server exception should be mapped to a java exception on the client side using the QName. To do so, requires that the fault message contains the QName.
What I wanted to point out is, that any server side custom exception, thrown by a SEI implementation (I only tried it out with SSB) is lost, because on the way back it is wrapped with a MBeanExeption. Thus, the returned fault message did no longer contain any useful information about the originating exception. Because RC1 and RC2 handled custom exception correctly, I still consider this to be a bug in the 4.0.0 release. The admitting terrible and even incorrect hack, I did just not to break existing client code, that worked perfectly with the web service deployed on JBoss RC1 and RC2. I really like JBoss AS and would appreciate to see this problem to be fixed. Werner View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852463#3852463 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852463 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
