I'm using the HTTP Connector, but I'll assume that it works similarly.
Exceptions from the MBeans are consumed by MX4J (I forget where
exactly, but it's in the code that does the operations for you).
Basically, if your operation throws an exception, MX4J just returns an
MBeanException as you're seeing. I thought of writing a custom
executor to pass the exceptions up the chain, but haven't bothered.
>[mailto:mx4j-user-admin@...] On Behalf Of=20
>Chandresh Patel (chapatel)
>Sent: Wednesday, 19 October, 2005 15:04
>Subject: [Mx4j-user] Unable to get Custom exception over SOAPConnector
>I am using MX4J SOAPConnector and its working fine except when=20
>any MBean throws custom exception, I am not getting it as is=20
>on Client side. I have defined custom exception in WSDD file=20
>For example, when following MBean method is invoked by client,=20
>when server throws InvalidInputException, client is getting=20
>public void createGroup(Group group) throws InvalidInputException
>Using TCPDump I found that Client gets following response from Server:
>Exception thrown in operation createGroup</faultstring>
>Does passing custom exception worked for anyone using=20
>SOAPConnector? If so, please let me know, what needs to be=20
>done for it to work.
>Thanks in advance for any help,