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???
> > > > >
> > > > > 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]
