2 Replies Latest reply on Aug 27, 2003 6:12 AM by cazacov

    Throwing user defined exception

    cazacov Newbie

      I have a Stateless Session Bean published as web-service. It has method that returns some string value. How can I notify clients, that someting is wrong and request can not be processed ?

      Can I throw some exception and catch it on client side ? If yes, how can I declare this exception in web-service.xml file ?

        • 1. Re: Throwing user defined exception
          macberry Newbie

          You don't need to do anything particular... You just throw an exception in the method of your bean and you catch (or except or whatever language you use) it on the client side...

          You don't need to declare anything in the web-service.xml.

          • 2. Re: Throwing user defined exception
            cazacov Newbie

            I create my own exception:

            class MyException extends Exception {
            public MyException(String str) {

            Then create some test bean that throws this exception:

            public String sayHello()
            throws test.MyException
            throw new test.MyException("Some text");

            When I try to call sayHello method from my Delphi client, in JBoss console I see long exception stack trace:
            13:50:36,913 ERROR [AxisServlet] Exception:
            faultCode: {http://xml.apache.org/axis/}Server.userException
            faultString: java.lang.reflect.InvocationTargetException
            faultActor: null
            stackTrace: java.lang.reflect.InvocationTargetException

            Client receives long XML document with all this stack trace lines. At the end there is some useful info:
            Caused by: java.lang.IllegalAccessError: tried to access class test.MyException from class $Proxy119
            at $Proxy119.sayHello(Unknown Source)
            ... 52 more


            So, on client side I can extract type of user exception, but server sends very long document instead of short answer that exception was thrown and saves stack trace in server.log file.

            It looks like critical situation. Ok, server continues to process my queries and client got some information, but the way I do it now does not look nice.