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,
Nobody asked one of the more obvious questions:
How much free RAM do you have? How full and/or fragmented is your
drive? Heavy and/or ineffcient swapping could also slow you down.
(Also, what kind of machine? Some Java implementations are faster than others.)
...R
On 2/14/07, Murray Collingwo
: 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
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 scre
n 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
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
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 developm
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/C
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
;
> > > > > > public class JettyLauncher {
> > > > > >
> > > > > > public static void main(String[] args) throws Exception {
> > > > > > String path = (args.length > 0 ? args[0] : "web");
> >
> > Connector connector = new SelectChannelConnector();
> > > > > connector.setPort(8080);
> > > > > server.setConnectors(new Connector[] { connector });
> > > > >
> > > > > HandlerCollection handlers =
tor = new SelectChannelConnector();
> > > > connector.setPort(8080);
> > > > server.setConnectors(new Connector[] { connector });
> > > >
> > > > HandlerCollection handlers = new HandlerCollection();
> > > > ContextHandlerCollection con
dlerCollection();
> > > ContextHandlerCollection contexts = new
> > > ContextHandlerCollection();
> > > handlers.setHandlers(new Handler[] { contexts, new
> > > DefaultHandler() });
> > > server.setHandler(handlers);
> > >
>
faultHandler() });
> > server.setHandler(handlers);
> >
> > new WebAppContext(contexts, path, "/");
> >
> > server.setStopAtShutdown(true);
> > server.setSendServerVersion(true);
> >
> > server.start();
> > ser
Handlers(new Handler[] { contexts, new
> DefaultHandler() });
> server.setHandler(handlers);
>
> new WebAppContext(contexts, path, "/");
>
> server.setStopAtShutdown(true);
> server.setSendServerVersion(true);
>
> server.start();
> server
rsion(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 Je
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
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
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
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
unz
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
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
22 matches
Mail list logo