i found a good way to get around the discussed problems. the custom exception shows up as the faultDetail of the axisFault which gets thrown. just above the transport layer i added a hook which turns axisFaults into business exceptions, which is what i needed to do anyway. at this point a simple sax handler takes the faultDetail and populates the business exception accordingly. what shows up on the client side is descriptive, qualified business exception.
thanks for shedding some light on this topic, without which it would propably have taking me more time. /heiko -- berlin.de - meine stadt im netz. Jetzt eigene eMail-adresse @berlin.de sichern! http://webmail.berlin.de
