Client catching Web Service User Exceptions [Java 6.0.17]

[Shaitan00]

I am trying to send an EXCEPTION from a Web Server to a Client using JAX-WS ...
When the exception is thrown by the server the client does catch it ... but the contents are not the expected message...

[Server.java]
package pck;

@WebService()
public class Server
{
    @WebMethod()
    public function() throws UserException
    {
    throw new UserException(“Something”);
    }
}
 
[Exception.java]
import javax.xml.ws.WebFault;
 
@WebFault()
public class UserException
        extends Exception
{
    private String ErrMessage;
 
    public UserException(String message)
    {
        this.ErrMessage = message;
    }
    
    public String ErrorMessage()
    {
        return this.ErrMessage;
    }
}
 
[Client.java]
public class Client
{
    public static void main(String[] args) throws Exception
    {
    try
        {
        Server.function();
        }
    catch (UserException ex)
        {
        System.out.println("User Exception: " + ex.ErrorMessage());
        }
    }
}

Now, as I mentioned, when the exception is thrown by the server the client does catch it, but ex.ErrorMessage() returns the string “pck.UserException” instead of “Something” which it was created with in the Server... any clues as to why?

Also, when I run my WebService I keep getting the following messages in the output:
com.sun.xml.internal.ws.model.RuntimeModeler getExceptionBeanClass
INFO: Dynamically creating exception bean Class pck.jaxws.UserExceptionBean

Any clues or help would be much appreciated.
Thanks,

[Tolls]

Print the stack trace and see what it is you're looking at? I never rely on the error message, since you lose far too much information that way.

It does seem odd, though, that it would alter the content of the exception. What does the WSDL look like? Specifically the bit that defines this wsdl:fault? That might give you a pointer to how JAX-WS has chosen to define the exception.

[Shaitan00]

The WSDL has a wsdl:fault for my exception, but no mention anywhere of the String ErrMessage ... I would have assumed it would be there ... but no matter what I try the WSDL never seems to "pick it up"

[Tolls]

What does the exception look like in a debugger at the client?

[Shaitan00]

Actually - it looks like using the super (Message) solved the problem ...