37 PM
Subject: Re: A survey about redeployment time in the Java EE world
> Em Thu, 24 Sep 2009 11:28:09 -0300, Vangel V. Ajanovski
> escreveu:
>
>> Hi, I would really like to have live class reloading but it doesn't work
>> for all classes because I use the pattern with
Yes, it works fine. I'm using all the latest stuff including m2eclipse
dev version and life's good :)
Kalle
On Thu, Sep 24, 2009 at 10:25 AM, Ilya Obshadko wrote:
>>
>> That's simply not true. I love Jetty and it's very well implemented
>> but the core Tomcat runs and starts up just as fast as
> And that is for development, for deployment I have a bigger problem because
> it is under Tomcat 6 which is behind AJP fronted by MS IIS.
> And if the application is packaged from maven as a WAR, then all the classes
> are inside packed in a JAR, which Tomcat extracts in a temporary place and
> s
>
> That's simply not true. I love Jetty and it's very well implemented
> but the core Tomcat runs and starts up just as fast as Jetty. I bet
> Ilya's issue is he tries to use Eclipse own JEE container support,
> which is using the traditional concept - copy files, redeploy
> application on change.
On Thu, Sep 24, 2009 at 6:49 AM, Thiago H. de Paula Figueiredo
wrote:
> Em Thu, 24 Sep 2009 10:46:31 -0300, Ilya Obshadko
> escreveu:
>> Live class reloading is a great feature.
>> But I couldn't figure out yet how one should configure, for example,
>> Tomcat 6 in development environment to avoid
Em Thu, 24 Sep 2009 11:28:09 -0300, Vangel V. Ajanovski
escreveu:
Hi, I would really like to have live class reloading but it doesn't work
for all classes because I use the pattern with Spring and Hibernate
described at:
http://wiki.apache.org/tapestry/Tapstry5First_project_with_Tapestry5%2C_
Em Thu, 24 Sep 2009 10:56:17 -0300, Ilya Obshadko
escreveu:
I'm totally OK with Jetty, but it demonstrates pretty the same behavior
if running inside Eclipse IDE server adaptor. Probably I'm missing
something
obvious?
I run Jetty in embedded mode: add it to the classpath (using Maven, w
On 24.09.2009 15:39, Thiago H. de Paula Figueiredo wrote:
http://www.zeroturnaround.com/blog/java-ee-container-redeploy-restart-turnaround-report/
It makes one very compelling reason to use Tapestry 5: live class
reloading avoids almost most redeploys related to the web tier. :)
Hi, I would
llya i use Sysdeo http://www.eclipsetotale.com/tomcatPlugin.html for
tomcat inside Eclipse.
It allows to detect changes in the java fiese without the need of a
context reload. The changes detected are limited but it's a pretty
boost for my productivity.
On Thu, Sep 24, 2009 at 3:56 PM, Ilya Obshad
>
> Live class reloading is a great feature.
>> But I couldn't figure out yet how one should configure, for example,
>> Tomcat 6 in development environment to avoid redeployments after each and
>> every
>> change in the code. Are there any solutions?
>>
>
> Use Jetty instead: faster, simpler, more
Em Thu, 24 Sep 2009 10:46:31 -0300, Ilya Obshadko
escreveu:
Live class reloading is a great feature.
But I couldn't figure out yet how one should configure, for example,
Tomcat 6 in development environment to avoid redeployments after each
and every
change in the code. Are there any solu
Live class reloading is a great feature.
But I couldn't figure out yet how one should configure, for example, Tomcat
6 in development environment to avoid redeployments after each and every
change in the code. Are there any solutions? I use Eclipse, if it makes
sense.
On Thu, Sep 24, 2009 at 5:39
http://www.zeroturnaround.com/blog/java-ee-container-redeploy-restart-turnaround-report/
It makes one very compelling reason to use Tapestry 5: live class
reloading avoids almost most redeploys related to the web tier. :)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer
13 matches
Mail list logo
