In general server side java exceptions do get propagated to the client. This is logical, because the client stack may not even have the notion of exceptions in their language.
To debug this properly, you should examine the fault message that is generated on the server side. It should contain the QName of the custom fault. On the client side that fault QName should be mapped to a java exeption. Note, it may have a different name and reside in a differnt package then the exception being thrown at the server side. The client code should be able to catch that user exception. See the wiki for an example. Werner, you are right. That change is a terrible hack :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852426#3852426 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852426 ------------------------------------------------------- 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
