Custom exception support have been fixed in 4.0.1 (soon to be released). Custom exceptions are used in the same way that custom beans are used. The only difference is that a constructor is searched for (instead of an accessor method) since java does not expose acesss to the exception message. All you have to do is create a custom exception, and make sure that you have a constructor for all values in your exception, as well as get methods.
An important thing to note is that wscompile is not very good about generating the correct order of the arguments. Which means that your constructor may be called with the arguments in the wrong order. If this occurs you will need to refer to <a href="http://www.jboss.org/wiki/Wiki.jsp?page=WSTypeMapping>WSTypeMapping in the wiki to create a ws4ee-deployment.xml file which controls the order. >From my observations, it appears that wscompile generates its wsdl in >subclass->superclass, type, name order. -Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3855276#3855276 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3855276 ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
