Hi Kevin > Any thoughts on what I may be doing wrong?
Just to confirm, are you sure you are compiling? Idea needs you to explicitly hit CRTL-SHIFT-F9 (to compile just one class) or CTRL-F9 (make project) That was my problem when I started working with Idea and Tapestry (both 4 and 5). BTW, I'm using the excelent JavaRebel for live class reloading when working with T4 on Idea Cheers. -- Alejandro Scandroli Amneris: We build process-driven web applications. http://www.amneris.es On Jan 16, 2008 11:34 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > Hi Michael, > > Thanks for the advice. I added Jetty6 as a test dependency and wrote my own > class that's a more domain-specific version of the JettyRunner. I didn't > take your approach 100% because that class is a Tapestry test artifact and > as such, not part of the primary distribution. > > Anyway, things are working quite well, but the class reloading doesn't work > for me. Template reloading works just fine, but not the class. I have > tested with page classes that are in the proper structure. > > Any thoughts on what I may be doing wrong? > > Thanks, > Kevin > > > On 1/16/08 3:04 PM, in article [EMAIL PROTECTED], "Michael Lake" > > <[EMAIL PROTECTED]> wrote: > > > > > For T5, in lieu of jettyLauncher you might try looking into extending > > the following class somewhere in your test sources: > > > > org.apache.tapestry.test.JettyRunner > > > > make a wrapper around it with a class that has a static main function. > > > > there's an example of it in "tapestry-core" sources > > > > org.apache.tapestry.integration.RunJetty > > > > > > At least this is how I run T5 in IDEA.. > > > > -mike > > > > Jesse Kuhnert wrote: > >> For tap 4: > >> > >> -) Use the latest eap release if you use maven - they make tiny > >> improvements to that minefield with each release. > >> -) Under project settings make sure you un-check the option to build a > >> "war" file for your web facet. (also don't create an exploded > >> directory to run it in) > >> -) Make sure your compiler settings compile ~everything~ you need to > >> the classpath. > >> -) You can configure your web facet to include all the necessary > >> resources as you need them. > >> > >> The overall thing I do is try and always run the web app from the > >> source directory structure "as is". Almost always invoke jetty > >> directly with IDEA using a normal application run configuration. (you > >> can have maven/ant compile tasks associated with this run as well - if > >> you need any special processing to happen) > >> > >> You should in theory be able to run the app using the same classpath > >> that the IDE uses and have Tapestry 5 (or 4 but with no fun re-load of > >> classes =( ) without ever having to rebuild the whole thing. Makes > >> things a ~lot~ easier when you work off the same directory structure > >> that the app is hosted (in version control) from. > >> > >> On Jan 16, 2008 2:33 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > >> > >>> Hi all, > >>> > >>> It's time for me to ask about IDEA and Tapestry again. I seem to go in > >>> cycles with the whole thing. > >>> > >>> Recent traffic indicates that there's now a decent number of people using > >>> IDEA with Tapestry. My question is simply, how? > >>> > >>> I've been using the third party Jetty integration plugin and set my webapp > >>> to rebuild upon frame deactivation (a setting I seem to have to make every > >>> time I start up IDEA because I'm using a Maven project). This works, but > >>> does a full redeploy on any change and that redeploy doesn't occur until I > >>> switch back to the browser window. So, a simple template change will > >>> rebuild my app, all its dependencies, and redeploy to Jetty. I'm running > >>> some decent metal here with a trivial sized app and it takes at least 10s > >>> before the app is back up. > >>> > >>> Moreover, I can only do this about 10 times before I either blow out the > >>> heap (T5) or permgen space (T4). At that point, I have to unceremoniously > >>> kill the Jetty process. > >>> > >>> The net of it is that disabling caching in T4 gains me nothing and live > >>> class reloading in T5 gains me nothing. In contrast, I still have a T4 > >>> app > >>> in Eclipse using JettyLauncher and I can run that without caching all day > >>> long. > >>> > >>> Without a doubt, I'm doing something wrong. Would anyone else mind > >>> sharing > >>> their setup so I can fix mine? > >>> > >>> Thanks, > >>> Kevin > >>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >> > >> > >> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
