MessageUtils needs StandardException.getArgumentFerry() to be precise.
How should we solve this ?
Hi Abhinav,
I wonder if we can handle this by introducing a new interface class.
Something like:
interface ExceptionCarrier
{
public static Exception getArgumentFerry( SQLException se );
}
And then:
public class StandardException extends Exception implements ExceptionCarrier
{ ... }
The ExceptionCarrier interface class would be in
o.a.d.shared.common.error.ExceptionCarrier.
That way MessageUtils would use the ExceptionCarrier interface, but we would
not need to move the entire Standard Exception class, which is large and
complex and closely tied to the engine internals, to the shared area.
What do you think about this idea?
bryan
