I have found a workaround for exception propagation (the message part):
As I have metionned earlier, the faultstring is never get passed correctly.
Here is why:
The generated exception stub using WSDL2Java is JAX-RPC compliant (the message
part name is getting mapped to a get<message name part>), this is no
problem.
The framework does not map this message part to the faultstring. A quick
fix (and maybe the right way to do it) is to turn the following generated
code.
But the good way to do it will be to use the reflection API in conjunction
with the name of the message.
Quick fix:
/**
* AuthenticationException.java
*
* This file was auto-generated from WSDL
* by the Apache Axis Wsdl2java emitter.
*/
package com.vodafone.security;
public class AuthenticationException extends org.apache.axis.AxisFault
{
public String login;
public java.lang.String getLogin() {
return this.login;
}
public AuthenticationException() {
}
public AuthenticationException(java.lang.String login)
{
this.login = login;
}
}
into
/**
* AuthenticationException.java
*
* This file was auto-generated from WSDL
* by the Apache Axis Wsdl2java emitter.
*/
package com.vodafone.security;
public class AuthenticationException extends org.apache.axis.AxisFault
{
public java.lang.String getLogin() {
return getFaultString(
}
public AuthenticationException() {
}
public AuthenticationException(java.lang.String login)
{
setFaultString(login);
}
}
