[ http://thecla.homeftp.net:8380/jira/browse/SPRING-44?page=comments#action_11034 ]
Peter Friese commented on SPRING-44:
currently, the advice should always be used as soon as there is a ClientServiceLocator. This is why I added a type restriction for the template in the andromda-cartridge.xml.
Since working with advices is so helpful, I was thinking about a way to let users declare which advices they want to use on a per-class basis - not only on the client side, but also on the server. Since this turned out to be a major enhancement to the entire cartridge, I kept my fingers from it.
> Add support for rich clients.
> Key: SPRING-44
> URL: http://thecla.homeftp.net:8380/jira/browse/SPRING-44
> Project: Spring Cartridge
> Type: New Feature
> Versions: 3.0RC1
> Reporter: Peter Friese
> Assignee: Chad Brandon
> Priority: Minor
> Attachments: spring-rcp-remoting.patch
> 1) Make the client service locator class-loader insensitive.
> Rationale: When running in an Eclipse RCP application, the client service locator cannot load the clientContext.xml. Due to the way Eclipse handles class laoding (each plug-in has it's own classloader), Spring cannot find the clientContext.xml and access the beans defined herein.
> 2) Add a ThrowsAdvice that catches all exceptions thrown by the remote services.
> Rationale: This makes error handling a trivial task. The advice can contain code to log errors and display error dialogs. Once this is implemented, application developers will never have to handle remote errors again :-)
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see: