Greetings, I want to use a custom ActionResolver implementation to be able to handle the following scenario: 1) I have an action bean impl ManageEntityActionBean<T> manages T (save/view/delete), where T can be any entity - Project, ProjectGroup etc. 2) I would like to leverage Guice's TypeLiteral to hold the parameterized type info an runtime to be able to instantiate appropriate ActionBean instances - ManageEntityActionBean<Project> and ManageEntityActionBean<ProjectGroup> etc. 3) Resolve paths to appropriate ActionBean instances in (2) above. Say, /manageProject.action to be handled by a ManageEntityActionBean<Project> instance, so on and so forth.
So I started off a custom ActionResolver implementation, but I quickly ran into limitations with the ActionResolver API. I think what I am missing is some sort of ActionResolutionContext (an arbitraty term!) to be exposed via the ActionResolver API, and then the custom ActionResolver implementation can do fancy things with it. In this above case, the ActionResolutionContext can hold the hints required to resolve to appropriate implementation. What do you guys reckon? Look forward to thoughts... Thanks, Rahul ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
