the problem with generating JSPs into the /src/jsp tree is that you need to be updating them manually when there has been a significant change in the model (and you need to be aware of that fact how bpm4struts works and updates JSPs)
wouldn't this be more difficult than simply selecting and putting JSP files in the /src/jsp tree manually using the copy-over feature ? all in all it has more advantages I think (easier to understand, you can always see both JSPs [original/custom], you can see which JSPs are custom by simply opening the /src/jsp tree) we worked like this in the beginning, but noticed that for project in production it really becomes a burden thinking about how to manage the JSPs, the current way needs attention too, but not that much (although I still agree we should find a better way to handle them) this is going to sound wild, but, maybe we could generate plain XML files that are processed using XSLT to generate actual JSPs ? this would allow us to write small external XSL files controlling the actual JSPs without touching the code generated by the cartridge such a thing would not be obvious to understand at first by the user, but it would allow the same level of abstraction as with the back-end cartridges using inheritance -- Wouter Zoons - [EMAIL PROTECTED] http://www.andromda.org/ _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=195#195 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
