I'm designing an application that will manage document approval lifecycle, it's very likely that MonoRail would be choosen as the web stack.
I need to plan about versionning issues of document input and approval forms, theses forms will be available as read only for completed documents and the application will have some changes in the future about which and how data is displayed on theses forms according to a revision number for the document/workflow instances. I really want to rely on simple view templates and not mess with some kind of generative meta model. My basic idea is to have dynamic resolution of templates location according to the document being displayed (it will have some workflow revision number to lookup, could be used to map over the directory structure of view templates), does it seems a crazy idea? Also, I'm pretty fond of strong typed views (likely aspview will be used), is there any pitfall going with "strong typed" property bag population with this kind of scenario? Finally I'm also sorting out this issue at the DB and service layer (I think MicroKernel child containers will be of help here) so any experience / feedback is welcome. Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
