I have made the following changes -
1. Cleaner exception structure. There is now a more logical exception hierarchy and exceptions contain context information about the current state of processing when the error occurred. for example there is a MessagingException base class that always contains a reference to the Message being processed. LifecycleExceptions such as InitilisationException contain a refernece to the objects whose lifecycle failed.
This can be useful information inside the Exception handlers.
2. The UMOExceptionStrategy class has gone and Mule uses the standard jave.bean.ExceptionListener interface. (this is the only change to the API that should effect users)
3. The Default exception strategies have been rewritten to use the new exception types.
4. All Exception messages have been i18n'd. Plus there is a simple mechanism to in place to internationalise strings in extensions and transport providers. All current sub-projects have been converted.
5. All Mule exceptions now have error codes, which means Mule now provides the facility to automatically map Mule exceptions to transport-specific return codes in request/response processing (i.e. Http status codes)
6. Exception printing has been improved so that the necessary information about the exception occurred is immediately available (this still needs a little work in the formatting- and I'm open to suggestions).
Improvement
Closed
Major
I have made the following changes -
1. Cleaner exception structure. There is now a more logical exception hierarchy and exceptions contain context information about the current state of processing when the error occurred. for example there is a MessagingException base class that always contains a reference to the Message being processed. LifecycleExceptions such as InitilisationException contain a refernece to the objects whose lifecycle failed.
This can be useful information inside the Exception handlers.
2. The UMOExceptionStrategy class has gone and Mule uses the standard jave.bean.ExceptionListener interface. (this is the only change to the API that should effect users)
3. The Default exception strategies have been rewritten to use the new exception types.
4. All Exception messages have been i18n'd. Plus there is a simple mechanism to in place to internationalise strings in extensions and transport providers. All current sub-projects have been converted.
5. All Mule exceptions now have error codes, which means Mule now provides the facility to automatically map Mule exceptions to transport-specific return codes in request/response processing (i.e. Http status codes)
6. Exception printing has been improved so that the necessary information about the exception occurred is immediately available (this still needs a little work in the formatting- and I'm open to suggestions).