disclaimer: i don't dev for work, my css/js skills are improving slowly multi module maven ear - totally separate view from business logic - that ability alone is what got me back into java development after 6 or so years of system administration (and PHP hacks in CMSes and CRMs). I split my dev between web and business
do some ejb3 stuff and deploy to glassfish - creates database tables etc. @PostConstruct for glassfish (maybe @Service for JBoss) and fill database tables. EJB3 phase one complete - stuff works! The hyper efficient part: mvn generate-tapestry-project mvn eclipse:eclipse import to eclipse copying file to workspace cd to workspace mvn jetty:run ahhhh tapestry running - great. create basic models and use the wonderful automatic class reloading of tapestry running with jetty. this feature alone saves a bucket of time - buckets...hours even!!!! This may seem a bit wasteful, but to come up with simple models that do 80% of what I need is great for completing the bulk of web dev and keeping the dev requirements low and easily manageable. "deploy less, deliver more" and is my favourite part of tapestry development. instant satisfaction, punch through the visuals...see results fast! i run mvn jetty:run from the command line because I can control it more (e.g. ^c kills it) and my IDE has one less thing to do and i can scroll up/down the CLI to see what's happening ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Now time for the less efficient part: When I'm ready, I wrestle with glassfish/ejb3 integration with a multi module ear set up. It's a helluva lot easier the last 6 months now that tapestry can handle the @EJB annotation - thanks whoever did that (heaps!!) I don't mind spending a slow half week linking the two sub projects together, I do other stuff to break up my hair pulling. The result: That is generally phase I or version 1 of a project Hacking between web and business layers at the same time takes a lot more concentration, time and debugging (for me) - and that's basically why i split the work up. *shrug* hope it helps in your tapestry reconnaissance Alex :) On 16/01/2012, at 6:55 PM, Bård Magnus Kvalheim wrote: > hi, > > * We have a multi module maven project(s). > * Use eclipse with m2e plugin. > * m2e plugin resolves workspace artifacts > * Use jetty to test apps. maven build, jetty:run from 'run configuration' > > We don't use any specific tapestry plugins. All about conventions so > CTRL+SHIFT+R(/T) works well > > However, for newcomers to tapestry and/or specific project it could be nice > with component overview, tabbed-mode for java/tml/js/css, template > suggestions/autocomplete (I know about the jstl/jsp taglib approach, but > it's not for own components). > > -- magnus > > On Mon, Jan 16, 2012 at 8:13 AM, Alex Kotchnev <akoch...@gmail.com> wrote: > >> I was wondering if folks would be willing to share how in general their >> tapestry projects are set up in terms of build setup and IDE usage ? With >> T5 it seems that most tutorials point to starting up w/ a Maven project and >> going from there. After you initially set up your project - did you keep >> going w/ the maven set up (using a Maven based project from an IDE), or do >> you convert it to an IDE specific project (e.g. generate an eclipse >> project) and continue using it that way . Now that T5 has moved to gradle >> as the build system - did you move your own projects to gradle (obviously >> you don't have to but still it's interesting to know). >> >> The reason I ask is that I'm really curious of what it would take to have a >> really kick-ass IDE support for Tapestry. IntelliJ already has some support >> for T5, so do Eclipse and NetBeans ; however, it is my impression that >> neither hits the nail on the head. >> >> I was thinking of creating a survey for this (which I might do if more than >> a couple of people respond ). If nothing else the results of such a survey >> could be interesting to have in the community. >> >> >> Cheers, >> >> Alex K >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
