tag:blogger.com,1999:blog-19648744.post2551557075595594762..comments2007-09-10T14:33:29.241-05:00akochnevhttp://www.blogger.com/profile/05519996133043093264noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-19648744.post-10579294930064823332007-09-10T14:33:00.000-05:002007-09-10T14:33:00.000-05:002007-09-10T14:33:00.000-05:00Peter, <BR/> thanks for the tip, I do evict the controllers plugin; however, I think it was one of the other scripts that optionally copies the "views" directory into WEB-APP in prod config, and adding the filter and not copying in the dev config. I thought that the Tapestry templates should be in views (and code should be in controllers) as that's where typical gsp-s/controllers sit, just to keep it as close to Grails as possible (considering that the gsp-s and the Tapestry templates have very similar functions, whereas quartz jobs and jsecurity realms are quite different)<BR/> <BR/> I'll definitely take a look at these other plugins for inspiration, I can definitely use some best-practices working examples. <BR/><BR/> Thanks for checking in !akochnevhttp://www.blogger.com/profile/05519996133043093264noreply@blogger.comtag:blogger.com,1999:blog-19648744.post-61100095732639417852007-09-10T13:58:00.000-05:002007-09-10T13:58:00.000-05:002007-09-10T13:58:00.000-05:00Hi Alex,<BR/><BR/>(1) seems fine, but I would consider evicting the controllers plugin and creating a custom artefact for your pages, possibly in a 'pages' sub-directory. The JSecurity and Quartz plugins have examples of custom artefacts (Realm in JSecurity, and Job in Quartz).<BR/><BR/>As for the scripts, the GWT plugin has some 'create*' scripts that you can use for inspiration.<BR/><BR/>Keep up the good work.Peterhttp://www.blogger.com/profile/07926972044560116057noreply@blogger.com