Re: Development environment for a modular Tapestry app
If you are using m2e maven eclipse plugin then it should do the right thing 1. If it can resolve the dependency from your eclipse workspace, it will use the local class files 2. If not (lets say you close / delete the project) then it will use the jar files from your maven repository The RunJettyRun plugin simply uses your m2e classpath. The only problem comes with loading modules from the jar's manifest. When using local class files the manifest is not read. So you need an explicit @SubModule annotation but I don't see this as a huge problem. You can add the @SubModule this to your DevelopmentModule if you like, It's also fine to put it in your production AppModule since tapestry IOC checks for duplicates and never loads a module twice.
Re: Development environment for a modular Tapestry app
BTW tapestry-stitch has two modules (component library + webapp) and I develop in eclipse using m2e + RunJettyRun. As you can see, StitchModule is added to the manifest here: https://github.com/uklance/tapestry-stitch/blob/master/pom.xml#L67 But also declared as a SubModule here for easy testing: https://github.com/uklance/tapestry-stitch-demo/blob/master/src/main/java/org/lazan/t5/stitch/demo/services/AppModule.java#L12
Development environment for a modular Tapestry app
I'm using Eclipse and Jetty. Back when I first started using Tapestry, I had ALL my code in on .war file. This made it easy to make use of the class reloading feature, which is to edit a java class\tml, and the effect takes place almost instantly ! But now my application is very modular, I have like 4 different modules deployed interchangeably for different clients and I'm serving them all at the same time. So to test a Tapestry web app, I configure different run configurations, each configuration having it's related modules (.jar) in it's class-path. Here comes the problem. When I edit my code, and build my module into a .jar file, the build is broken because the .jar file is already used by the loaded web app in jetty. So I can't make use of the class-reloading feature. And even if I do no include jars and just use Eclipse's projects. I have to edit almost all my modules by annotating them, to explicitly state the modules they depend on. This is VERY annoying and wastes a lot of time. I sometimes make mistakes so it could really waste a lot of time. Has anyone faced a similar situation and would care to share a better environment setup ? *-* *Muhammad Gelbana* http://eg.linkedin.com/in/mgelbana/
Re: Development environment for a modular Tapestry app
On Mon, 30 Sep 2013 14:28:34 -0300, Muhammad Gelbana m.gelb...@gmail.com wrote: Here comes the problem. When I edit my code, and build my module into a .jar file, the build is broken because the .jar file is already used by the loaded web app in jetty. So I can't make use of the class-reloading feature. It seems you're adding the same classes twice in the classpath. This should be avoided anyway. What are you using to launch Jetty? jetty:run sucks for multi-project development. RunJettyRun or embedded Jetty instance work wy better. And even if I do no include jars and just use Eclipse's projects. I have to edit almost all my modules by annotating them, to explicitly state the modules they depend on. You mean @Submodule? -- Thiago H. de Paula Figueiredo - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Development environment for a modular Tapestry app
On Mon, 30 Sep 2013 19:40:42 +0200, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Mon, 30 Sep 2013 14:28:34 -0300, Muhammad Gelbana m.gelb...@gmail.com wrote: Here comes the problem. When I edit my code, and build my module into a .jar file, the build is broken because the .jar file is already used by the loaded web app in jetty. So I can't make use of the class-reloading feature. It seems you're adding the same classes twice in the classpath. This should be avoided anyway. What are you using to launch Jetty? jetty:run sucks for multi-project development. RunJettyRun or embedded Jetty instance work wy better. Probably i have same issue. Actually I thought its not issue, its consequence. :) I'm using 'gradle jettyRun' and when jetty is running and i deploy tapestry module JAR with changed tapestry components. It ends up with 'Unable to resolve to a component class name.' exception. So as you said, can i deploy tapestry module without such error? Thanks for answer. And even if I do no include jars and just use Eclipse's projects. I have to edit almost all my modules by annotating them, to explicitly state the modules they depend on. You mean @Submodule? - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Development environment for a modular Tapestry app
@Thiago I'm using RunJettyRun. I think the other method you are referring to is maven's jetty:run ? Well I don't use maven at all. Yes I mean @Submodule. Editing my modules every time I need to load a specific set of modules is time consuming and error prone. I only need to be able to run my multi-module project, edit and make use of the class reloading feature without much effort. Having multiple configured setups (different sets of module in each run-configuration) is my aim here. Any method to test multi-module web projects will be just great. Would anyone care to share his setup ? :) *-* *Muhammad Gelbana* http://eg.linkedin.com/in/mgelbana/ On Mon, Sep 30, 2013 at 8:23 PM, Jan Fryblik jan.fryb...@ebrothers.czwrote: On Mon, 30 Sep 2013 19:40:42 +0200, Thiago H de Paula Figueiredo thiag...@gmail.com wrote: On Mon, 30 Sep 2013 14:28:34 -0300, Muhammad Gelbana m.gelb...@gmail.com wrote: Here comes the problem. When I edit my code, and build my module into a .jar file, the build is broken because the .jar file is already used by the loaded web app in jetty. So I can't make use of the class-reloading feature. It seems you're adding the same classes twice in the classpath. This should be avoided anyway. What are you using to launch Jetty? jetty:run sucks for multi-project development. RunJettyRun or embedded Jetty instance work wy better. Probably i have same issue. Actually I thought its not issue, its consequence. :) I'm using 'gradle jettyRun' and when jetty is running and i deploy tapestry module JAR with changed tapestry components. It ends up with 'Unable to resolve to a component class name.' exception. So as you said, can i deploy tapestry module without such error? Thanks for answer. And even if I do no include jars and just use Eclipse's projects. I have to edit almost all my modules by annotating them, to explicitly state the modules they depend on. You mean @Submodule? --**--**- To unsubscribe, e-mail: users-unsubscribe@tapestry.**apache.orgusers-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Development Environment
Luther, it is true - you can work with WTP and Tomcat 6, but that is like driving the BMW M5 without the M button being pressed. Try running the quick start T5 application with mvn jetty:run and with WTP/Tomcat. Try changing Start.java and then clicking the refresh button in the browser. Even in this one page web application with 2 java files it takes 10-times longer with WTP/Tomcat combo to display the changed Start page. I can imagine it gets worse with larger apps. And here is my point - if one of the main strengths of Tapestry 5 is live class reloading, then it is of paramount value to tell developers how can they harness the power in different development environments. This is where the documentation fails. I also own the Alexander's book and as much as the book is welcomed, it is outdated and the information given on page 43 is not true (at least in present moment): You will see that the change you have made is not reflected by the running application, because you have changed an HTML file, and not Java code. Smilar to NetBeans, Eclipse doesn't care about changes in HTML files. One way to update the application in such case is to follow the advice given for NetBeans - make change, even if it is an insignificant one, to some Java file, and save the file. The application will then be reloaded automatically. This is so not T5-ish. If there are many ways to develop T5 web apps, then some of this cases should be explained clearly as this is IMHO one of the barriers many new tapestry users are hitting at the very beginning. Of course some cases can be published on wiki, but the most common two or three must be on main T5 page - this is where most users start. I am filing a JIRA request for documentation improvement: https://issues.apache.org/jira/browse/TAP5-245 Cheers, Borut P.S. The Issues link on T5 page (http://tapestry.apache.org/tapestry5/) is wrong. It should be https://issues.apache.org/jira/browse/TAP5 2008/9/26 Luther Baker [EMAIL PROTECTED] For what its worth, I've had no trouble running Tomcat 6 with Eclipse WTP with MAVEN m2 plugins. I have NOT had to customize the tomcat instance at all. -Luther 2008/9/26 Jonathan Barker [EMAIL PROTECTED] I was recently cast out of the Garden of Eden for eating the forbidden fruit: m2eclipse (updated). I was running the old JettyLauncher with the old (and rather limited) m2eclipse, on Eclipse 3.3 / MyEclipse 6.0. Life was good. Easy debugging, hot reloading. I had JettyPlus configured so I could take my war file straight from my development system and drop it into a JBoss server for deployment and take advantage of pre-configured DataSources. Alas, the updated and mainly superior m2eclipse removes PluginDependencies from your classpath in order to make the execution within Eclipse be virtually identical to what it would be from command-line Maven. That breaks JettyLauncher and Run-Jetty-Run because you need the plugins on the classpath. Other than that, it does avoid some odd situations where things work in Eclipse but not when deployed elsewhere. I think I've figured out my usable alternative with external mvn hightide:run (hightide is a derivative of Jetty, and there is a hightide maven plugin). It's not as convenient, but it is workable. Jonathan -Original Message- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 13:59 To: Tapestry users Subject: Re: Development Environment Hi Borut, Please file JIRA issues for these ideas, otherwise they're bound to be lost. -- Kevin On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems to be great confussion. Cheers, Borut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Development Environment
:-) Nice analogy. So, how do I use the eclipse debugger with mvn jetty:run? Is it possible? Can I put a breakpoint in my source and have the application drop into it from mvn jetty:run? If not, I have relegated myself to use the simple tomcat solution for now. The button on an M5 is nice but I'd prefer to *work* on a 1969 muscle car if it means I can actually get under the hood and trace the inner workings (not quite as clever as your analogy, I know ;-) Agree with your sentiment. -Luther On Sat, Sep 27, 2008 at 9:38 AM, Borut Bolčina [EMAIL PROTECTED]wrote: Luther, it is true - you can work with WTP and Tomcat 6, but that is like driving the BMW M5 without the M button being pressed. Try running the quick start T5 application with mvn jetty:run and with WTP/Tomcat. Try changing Start.java and then clicking the refresh button in the browser. Even in this one page web application with 2 java files it takes 10-times longer with WTP/Tomcat combo to display the changed Start page. I can imagine it gets worse with larger apps. And here is my point - if one of the main strengths of Tapestry 5 is live class reloading, then it is of paramount value to tell developers how can they harness the power in different development environments. This is where the documentation fails. I also own the Alexander's book and as much as the book is welcomed, it is outdated and the information given on page 43 is not true (at least in present moment): You will see that the change you have made is not reflected by the running application, because you have changed an HTML file, and not Java code. Smilar to NetBeans, Eclipse doesn't care about changes in HTML files. One way to update the application in such case is to follow the advice given for NetBeans - make change, even if it is an insignificant one, to some Java file, and save the file. The application will then be reloaded automatically. This is so not T5-ish. If there are many ways to develop T5 web apps, then some of this cases should be explained clearly as this is IMHO one of the barriers many new tapestry users are hitting at the very beginning. Of course some cases can be published on wiki, but the most common two or three must be on main T5 page - this is where most users start. I am filing a JIRA request for documentation improvement: https://issues.apache.org/jira/browse/TAP5-245 Cheers, Borut P.S. The Issues link on T5 page (http://tapestry.apache.org/tapestry5/) is wrong. It should be https://issues.apache.org/jira/browse/TAP5 2008/9/26 Luther Baker [EMAIL PROTECTED] For what its worth, I've had no trouble running Tomcat 6 with Eclipse WTP with MAVEN m2 plugins. I have NOT had to customize the tomcat instance at all. -Luther 2008/9/26 Jonathan Barker [EMAIL PROTECTED] I was recently cast out of the Garden of Eden for eating the forbidden fruit: m2eclipse (updated). I was running the old JettyLauncher with the old (and rather limited) m2eclipse, on Eclipse 3.3 / MyEclipse 6.0. Life was good. Easy debugging, hot reloading. I had JettyPlus configured so I could take my war file straight from my development system and drop it into a JBoss server for deployment and take advantage of pre-configured DataSources. Alas, the updated and mainly superior m2eclipse removes PluginDependencies from your classpath in order to make the execution within Eclipse be virtually identical to what it would be from command-line Maven. That breaks JettyLauncher and Run-Jetty-Run because you need the plugins on the classpath. Other than that, it does avoid some odd situations where things work in Eclipse but not when deployed elsewhere. I think I've figured out my usable alternative with external mvn hightide:run (hightide is a derivative of Jetty, and there is a hightide maven plugin). It's not as convenient, but it is workable. Jonathan -Original Message- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 13:59 To: Tapestry users Subject: Re: Development Environment Hi Borut, Please file JIRA issues for these ideas, otherwise they're bound to be lost. -- Kevin On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems
Re: Development Environment
With m2eclipse: Right click your project, select Debug As -- Maven build... and start jetty:run from there On Sat, 27 Sep 2008 17:20:54 +0200, Luther Baker [EMAIL PROTECTED] wrote: :-) Nice analogy. So, how do I use the eclipse debugger with mvn jetty:run? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Development Environment
I love this forum! On Sep 27, 2008, at 10:44 AM, Martin Strand wrote: With m2eclipse: Right click your project, select Debug As -- Maven build... and start jetty:run from there On Sat, 27 Sep 2008 17:20:54 +0200, Luther Baker [EMAIL PROTECTED] wrote: :-) Nice analogy. So, how do I use the eclipse debugger with mvn jetty:run? - 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]
Re: Development Environment
Or mvnDebug jetty:run and then attach the debugger to the running jvm. Regards, Olle 2008/9/27 Luther Baker [EMAIL PROTECTED] I love this forum! On Sep 27, 2008, at 10:44 AM, Martin Strand wrote: With m2eclipse: Right click your project, select Debug As -- Maven build... and start jetty:run from there On Sat, 27 Sep 2008 17:20:54 +0200, Luther Baker [EMAIL PROTECTED] wrote: :-) Nice analogy. So, how do I use the eclipse debugger with mvn jetty:run? - 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] -- Olle Hallin M.Sc. +46 70 6653071 [EMAIL PROTECTED] www.hit.se
Re: Development Environment
I currently use Eclipse 3.4 J2EE, Run-Jetty-Run and Jetty 6 with no problems at all, I can debug quite happily through the debugger with class reloading (components/pages) and template (.tml) changes all happening live. The only thing I need to restart for is non-managed clesses such as Entities and Services - no biggie, jetty restarts virtually instantly on my machine. Have a look at: http://wiki.apache.org/tapestry/Tapestry5HowToSetupEclipseRunJettyRun -- View this message in context: http://www.nabble.com/Development-Environment-tp19686205p19704939.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Development Environment
Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems to be great confussion. Cheers, Borut
Re: Development Environment
Hi Borut, Please file JIRA issues for these ideas, otherwise they're bound to be lost. -- Kevin On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems to be great confussion. Cheers, Borut
RE: Development Environment
I was recently cast out of the Garden of Eden for eating the forbidden fruit: m2eclipse (updated). I was running the old JettyLauncher with the old (and rather limited) m2eclipse, on Eclipse 3.3 / MyEclipse 6.0. Life was good. Easy debugging, hot reloading. I had JettyPlus configured so I could take my war file straight from my development system and drop it into a JBoss server for deployment and take advantage of pre-configured DataSources. Alas, the updated and mainly superior m2eclipse removes PluginDependencies from your classpath in order to make the execution within Eclipse be virtually identical to what it would be from command-line Maven. That breaks JettyLauncher and Run-Jetty-Run because you need the plugins on the classpath. Other than that, it does avoid some odd situations where things work in Eclipse but not when deployed elsewhere. I think I've figured out my usable alternative with external mvn hightide:run (hightide is a derivative of Jetty, and there is a hightide maven plugin). It's not as convenient, but it is workable. Jonathan -Original Message- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 13:59 To: Tapestry users Subject: Re: Development Environment Hi Borut, Please file JIRA issues for these ideas, otherwise they're bound to be lost. -- Kevin On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems to be great confussion. Cheers, Borut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Development Environment
For what its worth, I've had no trouble running Tomcat 6 with Eclipse WTP with MAVEN m2 plugins. I have NOT had to customize the tomcat instance at all. -Luther 2008/9/26 Jonathan Barker [EMAIL PROTECTED] I was recently cast out of the Garden of Eden for eating the forbidden fruit: m2eclipse (updated). I was running the old JettyLauncher with the old (and rather limited) m2eclipse, on Eclipse 3.3 / MyEclipse 6.0. Life was good. Easy debugging, hot reloading. I had JettyPlus configured so I could take my war file straight from my development system and drop it into a JBoss server for deployment and take advantage of pre-configured DataSources. Alas, the updated and mainly superior m2eclipse removes PluginDependencies from your classpath in order to make the execution within Eclipse be virtually identical to what it would be from command-line Maven. That breaks JettyLauncher and Run-Jetty-Run because you need the plugins on the classpath. Other than that, it does avoid some odd situations where things work in Eclipse but not when deployed elsewhere. I think I've figured out my usable alternative with external mvn hightide:run (hightide is a derivative of Jetty, and there is a hightide maven plugin). It's not as convenient, but it is workable. Jonathan -Original Message- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Friday, September 26, 2008 13:59 To: Tapestry users Subject: Re: Development Environment Hi Borut, Please file JIRA issues for these ideas, otherwise they're bound to be lost. -- Kevin On Fri, Sep 26, 2008 at 6:53 AM, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, since JettyLauncher is not working with Eclipse Ganymede, this should be mentioned at http://tapestry.apache.org/tapestry5/tutorial1/env.html I looked at http://code.google.com/p/run-jetty-run/ but some posts suggest that it is not working with m2eclipse plugin.But I will try it out... It would be a great time saver if tutorial at the above link would describe some different scenarios how developers can set up their environments to benefit from live class reloading. Reading the mailing list there seems to be great confussion. Cheers, Borut - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My crap development environment
hi, as you are using windows, there are some new options what can slow down your system. We have expirience such slow downs, when using tortoisesvn and an on-access virus-scanner. It is always a good thing trying to disable these scanners if there are performance issues with saving files. Cheers, Markus Murray Collingwood schrieb: Hi all Does anybody else find this hellishly confusing? It makes me want to throw everything out and go back to a nice simple DOS system and a Turbo C compiler! How much simpler it was back then... Okay, I downloaded the latest Eclipse system, copied my project into a fresh workspace. Saving a file was back to a sub-second response. Actually I tried saving a second file to make sure it wasn't a fluke the first time. There was definitely a problem somewhere and it has now gone away. Okay, now the second part of the problem. Tomcat or Jetty??? I don't want to package every time I make a small change to a config file or HTML, so I want the servlet engine to use my files from my development area. My previous frustrations with restarting tomcat have encouraged me down the Jetty track - I downloaded Jetty 6 yesterday and the test system was working in about 5 minutes, pretty good. I then added a context.xml for my application and now when I start Jetty it simple crashes and refuses to start the application. I get an error like: 'No class for Servlet or Filter' I haven't been able to find any help on this error. I did find information on a Jetty-Maven-Plugin but form my reading this is all about packaging the application - I don't want to go there. I also found a number of recent comments about Maven2 saying it was still quite buggy. Do I press ahead trying to solve the Jetty stuff or do I revert back to a Tomcat system??? I'm developing in a Windows XP environment so this may limit me from some of the options suggested here. PS Thanks to everybody who has contributed so far - I really appreciate your ideas and suggestions. You really are a very friendly bunch of people. PPS My computer is an Intel 2.8ghz processor with 1gb ram and 80gb harddrive. It's not slow with other stuff. Cheers Murray Some of my understandings: Sysdeo-tomcat-plugin - packages app and restarts Tomcat WTP - packages app and restarts Tomcat Web Standard Tools - I was using this AJDT - never used it Jetty6 plugin - is this the Jetty-maven-plugin referred above of different? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: My crap development environment
Oh din not know that I will give it a try!! -Ursprüngliche Nachricht- Von: Joe Trewin [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 16. Februar 2007 11:15 An: Tapestry users Betreff: RE: My crap development environment Don't forget that if you launch your web app in debug mode from Eclipse (and probably other IDEs) with Jetty (and maybe Tomcat?) then *most* minor code changes, particularly to pages/components etc will be picked up automatically without a server restart. Eclipse will complain when it can't. So even if you're not debugging it's often useful to launch in debug mode, depending on which part of your system you're developing. -Original Message- From: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Sent: 16 February 2007 08:55 To: Tapestry users Subject: AW: My crap development environment I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I had this issue while using the AJDT plugin in combination with Maven because maven uses 2 output directories by default (one for the test classes) and AJDT didn't handle this properly triggering a complete rebuild. There is no reason it should take 15 seconds to SAVE an .html file
Re: AW: My crap development environment
Hot code replacement works with Tomcat as well (for minor changes). (I use it with the Sysdeo plugin.) Holger Stolzenberg írta: Oh din not know that I will give it a try!! -Ursprüngliche Nachricht- Von: Joe Trewin [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 16. Februar 2007 11:15 An: Tapestry users Betreff: RE: My crap development environment Don't forget that if you launch your web app in debug mode from Eclipse (and probably other IDEs) with Jetty (and maybe Tomcat?) then *most* minor code changes, particularly to pages/components etc will be picked up automatically without a server restart. Eclipse will complain when it can't. So even if you're not debugging it's often useful to launch in debug mode, depending on which part of your system you're developing. -Original Message- From: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Sent: 16 February 2007 08:55 To: Tapestry users Subject: AW: My crap development environment I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I
AW: My crap development environment
I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I had this issue while using the AJDT plugin in combination with Maven because maven uses 2 output directories by default (one for the test classes) and AJDT didn't handle this properly triggering a complete rebuild. There is no reason it should take 15 seconds to SAVE an .html file (Jetty plugin won't speed that up). From his numbers it looks like after saving/compiling/publishing tomcat starts up in less than 10 seconds which sounds completely reasonable depending on his application's initialization requirements. Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) On 2/15/07, James Carman [EMAIL PROTECTED] wrote: The current jetty plugin uses jetty6. On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote: If you want to use the JettyLauncher plugin for Eclipse - I think it only works with Jetty 5, not Jetty 6. If you want to use Jetty 6 then you can't use the plugin
RE: My crap development environment
Don't forget that if you launch your web app in debug mode from Eclipse (and probably other IDEs) with Jetty (and maybe Tomcat?) then *most* minor code changes, particularly to pages/components etc will be picked up automatically without a server restart. Eclipse will complain when it can't. So even if you're not debugging it's often useful to launch in debug mode, depending on which part of your system you're developing. -Original Message- From: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Sent: 16 February 2007 08:55 To: Tapestry users Subject: AW: My crap development environment I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I had this issue while using the AJDT plugin in combination with Maven because maven uses 2 output directories by default (one for the test classes) and AJDT didn't handle this properly triggering a complete rebuild. There is no reason it should take 15 seconds to SAVE an .html file (Jetty plugin won't speed that up). From his numbers it looks like after saving/compiling/publishing tomcat starts up in less than 10 seconds which sounds completely reasonable
Re: My crap development environment
Big or small, I think whether hot code swapping succeeds or fails depends mostly on if the class can be safely (i.e. no existing objects of that type in memory) unloaded at the time changes are compiled. Tomcat and Jetty work the same way in this regard (too!). Kalle On 2/16/07, Joe Trewin [EMAIL PROTECTED] wrote: Don't forget that if you launch your web app in debug mode from Eclipse (and probably other IDEs) with Jetty (and maybe Tomcat?) then *most* minor code changes, particularly to pages/components etc will be picked up automatically without a server restart. Eclipse will complain when it can't. So even if you're not debugging it's often useful to launch in debug mode, depending on which part of your system you're developing. -Original Message- From: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Sent: 16 February 2007 08:55 To: Tapestry users Subject: AW: My crap development environment I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I had this issue while using the AJDT plugin in combination with Maven because maven uses 2 output directories by default (one for the test classes) and AJDT didn't handle this properly triggering a complete rebuild. There is no reason it should
Re: My crap development environment
I use WTP with the integrated Tomcat, and it's fine as long as I don't have a lot of web apps running from it. (takes a couple seconds to start, and restarts when I've changed a java or html/jwc.) It doesn't seem to restart when I change a .css file though; the change is just picked up on a screen refresh. I think I went this route because of the examples I had seen online, espcially Kent Tong's book (Chapter 1). I wouldn't mind trying Jetty if I found a good tutorial. I tried setting up Jetty Launcher last night, but I found out it doesn't yet support Jetty 6. On 2/16/07, Holger Stolzenberg [EMAIL PROTECTED] wrote: I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: My crap development environment
We use Jetty embedded in JBoss. From a developer point of view, I can re-compile my code using maven and copy the war over to my version of JBoss in about 8 seconds. I kill and restart the server in 17 seconds. When I want to debug, I tell Eclipse to connect up to JBoss and everything works. Usually, when I try and deploy to the running VM it complains about trying to put the code back, sometimes it works. Not ideal, but seems to work fine. Mark J. Stang Senior Engineer/Architect office: +1 303.468.2900 mobile: +1 303.507.2833 Ping Identity -Original Message- From: Daniel Jue [mailto:[EMAIL PROTECTED] Sent: Fri 2/16/2007 10:11 AM To: Tapestry users Subject: Re: My crap development environment I use WTP with the integrated Tomcat, and it's fine as long as I don't have a lot of web apps running from it. (takes a couple seconds to start, and restarts when I've changed a java or html/jwc.) It doesn't seem to restart when I change a .css file though; the change is just picked up on a screen refresh. I think I went this route because of the examples I had seen online, espcially Kent Tong's book (Chapter 1). I wouldn't mind trying Jetty if I found a good tutorial. I tried setting up Jetty Launcher last night, but I found out it doesn't yet support Jetty 6. On 2/16/07, Holger Stolzenberg [EMAIL PROTECTED] wrote: I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: My crap development environment
You can configure which webapps to start when the tomcat is started. Just select the update/remove context definition from the project's context menu... Regards: Norbi Holger Stolzenberg írta: I think the WTP approach with the temporary tomcat installation is very good because you can defined which projects should be started with this tomcat, if you use one tomcat with sysdeo then all webapps will always be starte. -Ursprüngliche Nachricht- Von: Kalle Korhonen [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 15. Februar 2007 20:39 An: Tapestry users Betreff: Re: My crap development environment Sysdeo's plugin is no silver bullet, but I keep evaluating alternatives and so far I haven't found anything better. The most common gotchas with Sysdeo is installing devloader (which you will need) and maintaining the set of libraries to load (for which sysdeo-tomcat-plugin is used), setting the context path correctly and making sure you don't have servlet-api loaded with the devloader. I have developers asking about these over and over again. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I'll have to try the sysdeo plugin again. I used to use it but at some point I decided I preferred the WTP plugin (I don't quite remember now the reason). In any case, it's very possible it takes 45 seconds in the initial build/publish if he has a slow disk or a large set of libraries to copy over. After the initial build, however, it should take a second or so to copy over any incremental changes (that's why I think he has an incremental builder problem). On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Oh ok. Yea I never understood why WTP went with that approach. There's gotta be some file locking issues though if that takes 45 seconds - luckily I'm on Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything in-place (I have Jetty as well but don't see much of a difference in performance either way). And now with Discursive's sysdeo-tomcat-plugin it's ah all so nicely automated. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: When using eclipse Web Standard Tools, eclipse sets up a temporary Tomcat (or other app server) directory with configuration and your project files. Tomcat is then started from this directory. This is done so you can have more control of when your changes appear in Tomcat. You can have it set so every time it detects changes in your build it copies the affected files to the temporary directory, or you can have it so you publish manually (For example I have auto-build enabled so I don't necessarily want tomcat restarting every time it detects a change, so I publish manually after I have made the set of changes I want). So basically Publishing involves just synchronizing the files tomcat sees with the contents of your eclipse biuld directory. On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote: Just out of interest, what's this publishing step? Compilation is the only thing and occasional re-load of the context when hotswapping fails (like it does with Tomcat most of the time) that should be required. If you do something else, I think you haven't set up your environment correctly for development. Kalle On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote: I really don't think the Jetty plugin is going to solve his performance problems. Jetty might or might not be faster but in any case, not significantly enough to solve his problem. I am willing to bet that his problem is due to an incremental compile issue where his entire project is re-compiled every time he saves one file. He's talking about 60 seconds before the server even begins starting up. I had this issue while using the AJDT plugin in combination with Maven because maven uses 2 output directories by default (one for the test classes) and AJDT didn't handle this properly triggering a complete rebuild. There is no reason it should take 15 seconds to SAVE an .html file (Jetty plugin won't speed that up). From his numbers it looks like after saving/compiling/publishing tomcat starts up in less than 10 seconds which sounds completely reasonable depending on his application's initialization requirements. Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) On 2/15/07, James Carman [EMAIL PROTECTED] wrote: The current jetty plugin uses jetty6. On 2
Re: My crap development environment
Murray, I really enjoyed using Jetty with the Eclipse startup plugin on a project I did a while back. I would highly reccomend abandoing tomcat for development and using Jetty during your development. If you have dependencies to tomcat functionality you might want to mock it out during dev., it will definetly save you time.Get the Jetty plugin and I think you'll have alot of your issues resolved. best, -dh On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - 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]
RE: My crap development environment
If you want to use the JettyLauncher plugin for Eclipse - I think it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the Jetty plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote:
Hi all
I have suffered long and hard under Eclipse and Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published???
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the
tomcat server: 45 seconds Starting the tomcat server: 54
seconds (it
insists on publishing first)
Does everybody else experience these delays or is it just me?
It was suggested that I use maven2 - however I looked through the
maven2 flash presentation and it didn't mention anything
about making
my development work in Eclipse faster - it was more focused
on pulling
dependencies and easing the build process. And if I were
to install
maven2 would it change any of the above anyway???
Cheers
mc
-
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]
Re: My crap development environment
The current jetty plugin uses jetty6.
On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote:
If you want to use the JettyLauncher plugin for Eclipse - I think it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the Jetty plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote:
Hi all
I have suffered long and hard under Eclipse and Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published???
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the
tomcat server: 45 seconds Starting the tomcat server: 54
seconds (it
insists on publishing first)
Does everybody else experience these delays or is it just me?
It was suggested that I use maven2 - however I looked through the
maven2 flash presentation and it didn't mention anything
about making
my development work in Eclipse faster - it was more focused
on pulling
dependencies and easing the build process. And if I were
to install
maven2 would it change any of the above anyway???
Cheers
mc
-
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]
Re: My crap development environment
I really don't think the Jetty plugin is going to solve his
performance problems. Jetty might or might not be faster but in any
case, not significantly enough to solve his problem. I am willing to
bet that his problem is due to an incremental compile issue where his
entire project is re-compiled every time he saves one file. He's
talking about 60 seconds before the server even begins starting up. I
had this issue while using the AJDT plugin in combination with Maven
because maven uses 2 output directories by default (one for the test
classes) and AJDT didn't handle this properly triggering a complete
rebuild. There is no reason it should take 15 seconds to SAVE an .html
file (Jetty plugin won't speed that up). From his numbers it looks
like after saving/compiling/publishing tomcat starts up in less than
10 seconds which sounds completely reasonable depending on his
application's initialization requirements.
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the tomcat server: 45 seconds
Starting the tomcat server: 54 seconds (it insists on publishing first)
On 2/15/07, James Carman [EMAIL PROTECTED] wrote:
The current jetty plugin uses jetty6.
On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote:
If you want to use the JettyLauncher plugin for Eclipse - I think it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the Jetty plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote:
Hi all
I have suffered long and hard under Eclipse and Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published???
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the
tomcat server: 45 seconds Starting the tomcat server: 54
seconds (it
insists on publishing first)
Does everybody else experience these delays or is it just me?
It was suggested that I use maven2 - however I looked through the
maven2 flash presentation and it didn't mention anything
about making
my development work in Eclipse faster - it was more focused
on pulling
dependencies and easing the build process. And if I were
to install
maven2 would it change any of the above anyway???
Cheers
mc
-
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
Re: My crap development environment
Just out of interest, what's this publishing step? Compilation is the only
thing and occasional re-load of the context when hotswapping fails (like it
does with Tomcat most of the time) that should be required. If you do
something else, I think you haven't set up your environment correctly for
development.
Kalle
On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote:
I really don't think the Jetty plugin is going to solve his
performance problems. Jetty might or might not be faster but in any
case, not significantly enough to solve his problem. I am willing to
bet that his problem is due to an incremental compile issue where his
entire project is re-compiled every time he saves one file. He's
talking about 60 seconds before the server even begins starting up. I
had this issue while using the AJDT plugin in combination with Maven
because maven uses 2 output directories by default (one for the test
classes) and AJDT didn't handle this properly triggering a complete
rebuild. There is no reason it should take 15 seconds to SAVE an .html
file (Jetty plugin won't speed that up). From his numbers it looks
like after saving/compiling/publishing tomcat starts up in less than
10 seconds which sounds completely reasonable depending on his
application's initialization requirements.
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the tomcat server: 45 seconds
Starting the tomcat server: 54 seconds (it insists on publishing first)
On 2/15/07, James Carman [EMAIL PROTECTED] wrote:
The current jetty plugin uses jetty6.
On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote:
If you want to use the JettyLauncher plugin for Eclipse - I think it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the Jetty
plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote:
Hi all
I have suffered long and hard under Eclipse and Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published???
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the
tomcat server: 45 seconds Starting the tomcat server: 54
seconds (it
insists on publishing first)
Does everybody else experience these delays or is it just me?
It was suggested that I use maven2 - however I looked through the
maven2 flash presentation and it didn't mention anything
about making
my development work in Eclipse faster - it was more focused
on pulling
dependencies and easing the build process. And if I were
to install
maven2 would it change any of the above anyway???
Cheers
mc
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands
Re: My crap development environment
When using eclipse Web Standard Tools, eclipse sets up a temporary
Tomcat (or other app server) directory with configuration and your
project files. Tomcat is then started from this directory. This is
done so you can have more control of when your changes appear in
Tomcat. You can have it set so every time it detects changes in your
build it copies the affected files to the temporary directory, or you
can have it so you publish manually (For example I have auto-build
enabled so I don't necessarily want tomcat restarting every time it
detects a change, so I publish manually after I have made the set of
changes I want). So basically Publishing involves just synchronizing
the files tomcat sees with the contents of your eclipse biuld
directory.
On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote:
Just out of interest, what's this publishing step? Compilation is the only
thing and occasional re-load of the context when hotswapping fails (like it
does with Tomcat most of the time) that should be required. If you do
something else, I think you haven't set up your environment correctly for
development.
Kalle
On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote:
I really don't think the Jetty plugin is going to solve his
performance problems. Jetty might or might not be faster but in any
case, not significantly enough to solve his problem. I am willing to
bet that his problem is due to an incremental compile issue where his
entire project is re-compiled every time he saves one file. He's
talking about 60 seconds before the server even begins starting up. I
had this issue while using the AJDT plugin in combination with Maven
because maven uses 2 output directories by default (one for the test
classes) and AJDT didn't handle this properly triggering a complete
rebuild. There is no reason it should take 15 seconds to SAVE an .html
file (Jetty plugin won't speed that up). From his numbers it looks
like after saving/compiling/publishing tomcat starts up in less than
10 seconds which sounds completely reasonable depending on his
application's initialization requirements.
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the tomcat server: 45 seconds
Starting the tomcat server: 54 seconds (it insists on publishing first)
On 2/15/07, James Carman [EMAIL PROTECTED] wrote:
The current jetty plugin uses jetty6.
On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote:
If you want to use the JettyLauncher plugin for Eclipse - I think it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the Jetty
plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote:
Hi all
I have suffered long and hard under Eclipse and Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published
Re: My crap development environment
Oh ok. Yea I never understood why WTP went with that approach. There's gotta
be some file locking issues though if that takes 45 seconds - luckily I'm on
Linux so I don't care. I use Sysdeo's Tomcat plugin that runs everything
in-place (I have Jetty as well but don't see much of a difference in
performance either way). And now with Discursive's sysdeo-tomcat-plugin it's
ah all so nicely automated.
Kalle
On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote:
When using eclipse Web Standard Tools, eclipse sets up a temporary
Tomcat (or other app server) directory with configuration and your
project files. Tomcat is then started from this directory. This is
done so you can have more control of when your changes appear in
Tomcat. You can have it set so every time it detects changes in your
build it copies the affected files to the temporary directory, or you
can have it so you publish manually (For example I have auto-build
enabled so I don't necessarily want tomcat restarting every time it
detects a change, so I publish manually after I have made the set of
changes I want). So basically Publishing involves just synchronizing
the files tomcat sees with the contents of your eclipse biuld
directory.
On 2/15/07, Kalle Korhonen [EMAIL PROTECTED] wrote:
Just out of interest, what's this publishing step? Compilation is the
only
thing and occasional re-load of the context when hotswapping fails (like
it
does with Tomcat most of the time) that should be required. If you do
something else, I think you haven't set up your environment correctly
for
development.
Kalle
On 2/15/07, Daniel Tabuenca [EMAIL PROTECTED] wrote:
I really don't think the Jetty plugin is going to solve his
performance problems. Jetty might or might not be faster but in any
case, not significantly enough to solve his problem. I am willing to
bet that his problem is due to an incremental compile issue where his
entire project is re-compiled every time he saves one file. He's
talking about 60 seconds before the server even begins starting up. I
had this issue while using the AJDT plugin in combination with Maven
because maven uses 2 output directories by default (one for the test
classes) and AJDT didn't handle this properly triggering a complete
rebuild. There is no reason it should take 15 seconds to SAVE an .html
file (Jetty plugin won't speed that up). From his numbers it looks
like after saving/compiling/publishing tomcat starts up in less than
10 seconds which sounds completely reasonable depending on his
application's initialization requirements.
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the tomcat server: 45 seconds
Starting the tomcat server: 54 seconds (it insists on publishing
first)
On 2/15/07, James Carman [EMAIL PROTECTED] wrote:
The current jetty plugin uses jetty6.
On 2/15/07, Joe Trewin [EMAIL PROTECTED] wrote:
If you want to use the JettyLauncher plugin for Eclipse - I think
it
only works with Jetty 5, not Jetty 6.
If you want to use Jetty 6 then you can't use the plugin, but you
can
launch from Eclipse easily enough just by making your own little
launcher class - for example:
import org.mortbay.jetty.Connector;
import org.mortbay.jetty.Handler;
import org.mortbay.jetty.Server;
import org.mortbay.jetty.handler.ContextHandlerCollection;
import org.mortbay.jetty.handler.DefaultHandler;
import org.mortbay.jetty.handler.HandlerCollection;
import org.mortbay.jetty.nio.SelectChannelConnector;
import org.mortbay.jetty.webapp.WebAppContext;
public class JettyLauncher {
public static void main(String[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development
Re: My crap development environment
); new WebAppContext(contexts, path, /); server.setStopAtShutdown(true); server.setSendServerVersion(true); server.start(); server.join(); } } -Original Message- From: Daniel Honig [mailto:[EMAIL PROTECTED] Sent: 15 February 2007 14:33 To: Tapestry users Subject: Re: My crap development environment Murray, I really enjoyed using Jetty with the Eclipse startup plugin on a project I did a while back. I would highly reccomend abandoing tomcat for development and using Jetty during your development. If you have dependencies to tomcat functionality you might want to mock it out during dev., it will definetly save you time.Get the Jetty plugin and I think you'll have alot of your issues resolved. best, -dh On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - 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] - 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]
Re: My crap development environment
[] args) throws Exception {
String path = (args.length 0 ? args[0] : web);
Server server = new Server();
Connector connector = new SelectChannelConnector();
connector.setPort(8080);
server.setConnectors(new Connector[] { connector });
HandlerCollection handlers = new HandlerCollection();
ContextHandlerCollection contexts = new
ContextHandlerCollection();
handlers.setHandlers(new Handler[] { contexts, new
DefaultHandler() });
server.setHandler(handlers);
new WebAppContext(contexts, path, /);
server.setStopAtShutdown(true);
server.setSendServerVersion(true);
server.start();
server.join();
}
}
-Original Message-
From: Daniel Honig [mailto:[EMAIL PROTECTED]
Sent: 15 February 2007 14:33
To: Tapestry users
Subject: Re: My crap development environment
Murray,
I really enjoyed using Jetty with the Eclipse startup
plugin on a project I did a while back. I would highly
reccomend abandoing tomcat for development and using Jetty
during your development. If you have dependencies to tomcat
functionality you might want to mock it out
during dev., it will definetly save you time.Get the
Jetty
plugin
and I think you'll have alot of your issues resolved.
best,
-dh
On 2/14/07, Murray Collingwood [EMAIL PROTECTED]
wrote:
Hi all
I have suffered long and hard under Eclipse and
Tomcat. Is
it really
necessary for me to wait so long while a file is saved or
an application is published???
Saving a .java file: 15 seconds
Saving a .html file: 15 seconds
Saving a .jwc file: 28 seconds
Stopping the tomcat server: 2 seconds (acceptable)
Publishing to the
tomcat server: 45 seconds Starting the tomcat server: 54
seconds (it
insists on publishing first)
Does everybody else experience these delays or is it just
me?
It was suggested that I use maven2 - however I looked
through
the
maven2 flash presentation and it didn't mention anything
about making
my development work in Eclipse faster - it was more
focused
on pulling
dependencies and easing the build process. And if I were
to install
maven2 would it change any of the above anyway???
Cheers
mc
-
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]
-
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]
Re: My crap development environment
Hi all Does anybody else find this hellishly confusing? It makes me want to throw everything out and go back to a nice simple DOS system and a Turbo C compiler! How much simpler it was back then... Okay, I downloaded the latest Eclipse system, copied my project into a fresh workspace. Saving a file was back to a sub-second response. Actually I tried saving a second file to make sure it wasn't a fluke the first time. There was definitely a problem somewhere and it has now gone away. Okay, now the second part of the problem. Tomcat or Jetty??? I don't want to package every time I make a small change to a config file or HTML, so I want the servlet engine to use my files from my development area. My previous frustrations with restarting tomcat have encouraged me down the Jetty track - I downloaded Jetty 6 yesterday and the test system was working in about 5 minutes, pretty good. I then added a context.xml for my application and now when I start Jetty it simple crashes and refuses to start the application. I get an error like: 'No class for Servlet or Filter' I haven't been able to find any help on this error. I did find information on a Jetty-Maven-Plugin but form my reading this is all about packaging the application - I don't want to go there. I also found a number of recent comments about Maven2 saying it was still quite buggy. Do I press ahead trying to solve the Jetty stuff or do I revert back to a Tomcat system??? I'm developing in a Windows XP environment so this may limit me from some of the options suggested here. PS Thanks to everybody who has contributed so far - I really appreciate your ideas and suggestions. You really are a very friendly bunch of people. PPS My computer is an Intel 2.8ghz processor with 1gb ram and 80gb harddrive. It's not slow with other stuff. Cheers Murray Some of my understandings: Sysdeo-tomcat-plugin - packages app and restarts Tomcat WTP - packages app and restarts Tomcat Web Standard Tools - I was using this AJDT - never used it Jetty6 plugin - is this the Jetty-maven-plugin referred above of different? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My crap development environment
Confusion avoidance (my approach): Eclipse - simply do not use. IntelliJ works more reliably and predictably, it works as expected and has controls where expected. Jetty vs Tomcat vs ... - Tomcat, removing everything from webapps/ and all the admin application context configurations from conf/Catalina/localhost makes it as fast as Jetty for all practical purposes. Plugins, deployments etc. - one extra command line window that has rinning command catalina.(sh|bat) run takes care of everything. --- Murray Collingwood [EMAIL PROTECTED] wrote: Hi all Does anybody else find this hellishly confusing? It makes me want to throw everything out and go back to a nice simple DOS system and a Turbo C compiler! How much simpler it was back then... Okay, I downloaded the latest Eclipse system, copied my project into a fresh workspace. Saving a file was back to a sub-second response. Actually I tried saving a second file to make sure it wasn't a fluke the first time. There was definitely a problem somewhere and it has now gone away. Okay, now the second part of the problem. Tomcat or Jetty??? I don't want to package every time I make a small change to a config file or HTML, so I want the servlet engine to use my files from my development area. My previous frustrations with restarting tomcat have encouraged me down the Jetty track - I downloaded Jetty 6 yesterday and the test system was working in about 5 minutes, pretty good. I then added a context.xml for my application and now when I start Jetty it simple crashes and refuses to start the application. I get an error like: 'No class for Servlet or Filter' I haven't been able to find any help on this error. I did find information on a Jetty-Maven-Plugin but form my reading this is all about packaging the application - I don't want to go there. I also found a number of recent comments about Maven2 saying it was still quite buggy. Do I press ahead trying to solve the Jetty stuff or do I revert back to a Tomcat system??? I'm developing in a Windows XP environment so this may limit me from some of the options suggested here. PS Thanks to everybody who has contributed so far - I really appreciate your ideas and suggestions. You really are a very friendly bunch of people. PPS My computer is an Intel 2.8ghz processor with 1gb ram and 80gb harddrive. It's not slow with other stuff. Cheers Murray Some of my understandings: Sysdeo-tomcat-plugin - packages app and restarts Tomcat WTP - packages app and restarts Tomcat Web Standard Tools - I was using this AJDT - never used it Jetty6 plugin - is this the Jetty-maven-plugin referred above of different? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Konstantin Ignatyev PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000 Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My crap development environment
I have nothing against Jetty, but honestly, for most users there is not a terribly significant difference in performance or ease of use between Jetty and Tomcat. Those who tell you that changing from Jetty to Tomcat to any other container out there will make a significant impact on your development time are selling false hope. The startup time of both containers is usually insignificantly small compared to the startup and initialization time of your application classes. My tomcat container takes 1 second to startup on my computer. So even if Jetty were twice as fast, I would have gained half a second, the rest of my application takes 9 seconds to startup so you can see that changing containers won't help me much. Now I am focusing just on startup time. From looking through the docs, it doesn't seem like Jetty is any more magical in class loading such that it would require less restarts than with tomcat. I'm not an expert so if someone has information regarding Jetty and class loading I'd be interested in hearing it. I actually use both containers. I use Tomcat in eclipse because it integrates extremely easily with WTP. I use Jetty to run from the command-line because of it's dead-simple integration with maven. I really can't tell any difference between them. They both seem to run just as fast and startup just as quickly. If there's any difference at all it is probably noticeable under a heavier load and not really during development. On 2/15/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all Does anybody else find this hellishly confusing? It makes me want to throw everything out and go back to a nice simple DOS system and a Turbo C compiler! How much simpler it was back then... Okay, I downloaded the latest Eclipse system, copied my project into a fresh workspace. Saving a file was back to a sub-second response. Actually I tried saving a second file to make sure it wasn't a fluke the first time. There was definitely a problem somewhere and it has now gone away. Okay, now the second part of the problem. Tomcat or Jetty??? I don't want to package every time I make a small change to a config file or HTML, so I want the servlet engine to use my files from my development area. My previous frustrations with restarting tomcat have encouraged me down the Jetty track - I downloaded Jetty 6 yesterday and the test system was working in about 5 minutes, pretty good. I then added a context.xml for my application and now when I start Jetty it simple crashes and refuses to start the application. I get an error like: 'No class for Servlet or Filter' I haven't been able to find any help on this error. I did find information on a Jetty-Maven-Plugin but form my reading this is all about packaging the application - I don't want to go there. I also found a number of recent comments about Maven2 saying it was still quite buggy. Do I press ahead trying to solve the Jetty stuff or do I revert back to a Tomcat system??? I'm developing in a Windows XP environment so this may limit me from some of the options suggested here. PS Thanks to everybody who has contributed so far - I really appreciate your ideas and suggestions. You really are a very friendly bunch of people. PPS My computer is an Intel 2.8ghz processor with 1gb ram and 80gb harddrive. It's not slow with other stuff. Cheers Murray Some of my understandings: Sysdeo-tomcat-plugin - packages app and restarts Tomcat WTP - packages app and restarts Tomcat Web Standard Tools - I was using this AJDT - never used it Jetty6 plugin - is this the Jetty-maven-plugin referred above of different? - 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]
My crap development environment
Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My crap development environment
You could run mvn jetty:run to fire up your application in Jetty. It works pretty well and it automatically picks up any changes you make and redeploys your webapp. On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - 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]
Re: My crap development environment
I recently suffered under Windows from unacceptable long file operations (any of them) - it turned out to be related to the mapped but inaccessible network drive. Win is extremely stupid and ALWAYS tries to reach that drive no matter if it required for file operation or not. So - try to unmap all the network drives and see it that will help :) --- Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Konstantin Ignatyev PS: If this is a typical day on planet earth, humans will add fifteen million tons of carbon to the atmosphere, destroy 115 square miles of tropical rainforest, create seventy-two miles of desert, eliminate between forty to one hundred species, erode seventy-one million tons of topsoil, add 2,700 tons of CFCs to the stratosphere, and increase their population by 263,000 Bowers, C.A. The Culture of Denial: Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools. New York: State University of New York Press, 1997: (4) (5) (p.206) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: My crap development environment
I would commit your project to a svn repository (or copy the project somewhere else) and grab a new version of Eclipse. I have no troubles like this under eclipse/tomcat, so somehow your installation must have gotten borked. In fact, if there is nothing wrong with your workspace you can just unzip a new eclipse and have it point to that workspace. (only one instance can access it at a time) P.S. I am using the latest Eclipse WTP, Tomcat 5.5.17, Tap 4.0. I am also using the latest subclipse. Have you checked your hardware logs? I've had disk hardware issues that cause my performace to degenerate into long waits like that. On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - 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]
Re: My crap development environment
Are you by any chance using AspectJ and the AJDT plugin? For me that was the problem with saving files due to a bug that happened in combiantion to Maven. If this is your case let me know and I'll post how to work around it. Publishing should be pretty darn quick on an incremental build (1 second or 2 at the max). As for tomcat startup, that depends on your particular application. A basic application should start up pretty quick.. .a few 3-15 seconds. While a more advanced application that does a lot of initialization such as initializing spring beans or hibernate will take much longer. Of course, this is all relative to your CPU and Disk speed. In any case, I've found that most problems with unacceptable performance in eclipse are due to a bug in some plugin you are using. On 2/14/07, Daniel Jue [EMAIL PROTECTED] wrote: I would commit your project to a svn repository (or copy the project somewhere else) and grab a new version of Eclipse. I have no troubles like this under eclipse/tomcat, so somehow your installation must have gotten borked. In fact, if there is nothing wrong with your workspace you can just unzip a new eclipse and have it point to that workspace. (only one instance can access it at a time) P.S. I am using the latest Eclipse WTP, Tomcat 5.5.17, Tap 4.0. I am also using the latest subclipse. Have you checked your hardware logs? I've had disk hardware issues that cause my performace to degenerate into long waits like that. On 2/14/07, Murray Collingwood [EMAIL PROTECTED] wrote: Hi all I have suffered long and hard under Eclipse and Tomcat. Is it really necessary for me to wait so long while a file is saved or an application is published??? Saving a .java file: 15 seconds Saving a .html file: 15 seconds Saving a .jwc file: 28 seconds Stopping the tomcat server: 2 seconds (acceptable) Publishing to the tomcat server: 45 seconds Starting the tomcat server: 54 seconds (it insists on publishing first) Does everybody else experience these delays or is it just me? It was suggested that I use maven2 - however I looked through the maven2 flash presentation and it didn't mention anything about making my development work in Eclipse faster - it was more focused on pulling dependencies and easing the build process. And if I were to install maven2 would it change any of the above anyway??? Cheers mc - 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]
Poll: T4 Development Environment
Hi all, I'm new to Tapestry, doing mostly a lot of initial research atm. Really impressed with the framework so far, and I'd like to start diving deeper. I think it would be a good discussion to see what kind of dev. setups everybody uses out in the wild, and motivation behind why they chose one over the other(s). I propose this simple format: Currently using: [IDE], [Tool1], [Tool2], [...] + stable + code completion - commercial etc. Tried: [IDE-1], [Tool1-1], [Tool2-1], [...-1] + fast - no documentation etc. Tried: [IDE-2], [Tool1-2], [Tool2-2], [...-2] Etc. Here's mine: Currently using: Eclipse, WTP, Subclipse, Tomcat 5.5 (same as at http://wiki.apache.org/tapestry/HowToSetupEclipseWtp) + pretty good for development and debugging: *basic* xml/html/java tools + see changes right away (T4 caching off + project auto-build) + nice integration with servlet container (Tomcat, any other, etc.) + open source - really miss smart code completion intentions for Java in IntelliJ Idea - no code completion for Tapestry-specific files, like in Spindle - when T4 is configured as a User Library, can't use it to run; have to put jars into WEB-INF/lib - WTP publishing is not instantaneous, as it has to move modified files to a temp dir first Tried: IntelliJ Idea, Tomcat 5.5 + great for Java coding - mediocre for XML and tapestry-specific files - commercial license Tried: Eclipse, Spindle 3, Tomcat (Tapestry 3) + Tap. code completion - very unstable Regards, - A - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
