#38 Web Service SOAPFaultException message changes

[caydin]

1. Format the Web Service SOAPFaultException messages
as follows:

catch(BSException e)
{
if (e == null)
{
throw createSOAPFaultException("Service
execution error. Encountered an application error.",e);
}
else
{
throw createSOAPFaultException(e.getMessage(),e);
}
}
catch(DataTypeFieldValidationException e)
{
throw createSOAPFaultException("Service execution
error. Input data validation error. " + e.getMessage
(),e);
}
catch(NamingException e)
{
throw createSOAPFaultException("Service execution
error. Unable to lookup underlying implementation of
the service. " + e.getMessage(),e);
}
catch(Throwable t)
{
throw createSOAPFaultException("Service execution
error. Caught unexpected exception. " + t.getMessage
(),t);
}

2. In the createSOAPFaultException method, log
exceptions as per log4J settings.
When logging exceptions, specify the class name,
method name, user detail, timestamp etc

[Rost Vashevnik]

Logged In: YES
user_id=883678

Hello !

This message is to notify you that someone from MetaBoss team
have had a look at your bug report, it was accepted and is
now awaiting the resolution. This means that someone from the
MetaBoss team will have a closer look at it and formulate a
response to you (most likely within 48 hours).

Please note that in addition to the Sourceforge support facilities
we maintain a FAQ and Forum at www.metaboss.com. If you have
not already done so, we suggest that you visit our site and search
for possible workarounds.

Please also note that all MetaBoss users are free to use any
support channel they like, however, in order to enjoy VIP Support,
MetaBoss Commercial License Holders must submit their questions
to the Forum at www.metaboss.com.

Thank you for your contribution to MetaBoss

MetaBoss team