Currently, the network client code is not able to access the arguments
that are associated with a Derby exception that is returned by the engine.
We would like to change the network client code, specifically the code
in the Sqlca and SqlException classes, so that it uses the new MessageUtils
class to access the exception arguments.
We wish to take the exception arguments and associate them with the
SqlException object, so that when the client calls the SQLExceptionFactory
to create a SQLException to throw to the user application, it can create
a Derby-specific subclass of that exception, when appropriate, which
contains the arguments that the server sent to the client.