You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Bryan Lewis <jb...@gmail.com> on 2011/10/10 20:42:19 UTC
running eclipse in production
This might be a silly idea, but I'll ask it anyway... Would it be bad to
run a Tapestry application inside Eclipse on a production server? The
objective would be to have full hot-swapping, as I have in my local
development workspace, but maybe it would be bad for memory consumption or
stability.
Re: running eclipse in production
Posted by Chris Mylonas <ch...@opencsta.org>.
Also in your container you can set it up for debugging - i.e. attach to port number X, for debugging with eclipse.
If that's what your intention was as well.
On 11/10/2011, at 6:25 AM, Howard Lewis Ship wrote:
> That would be a very silly idea, and not necessary. If you deploy an
> exploded WAR (with application class files and resources on the file
> system, not inside a WAR file) you can get hot swapping (but you'll
> need to run in development mode in 5.3, which turns off live class
> reloading in production).
>
> On Mon, Oct 10, 2011 at 12:17 PM, Dmitry Gusev <dm...@gmail.com> wrote:
>> Eclipse is not a web container, so you're not running Tapestry in Eclipse
>> anyway.
>>
>> On Mon, Oct 10, 2011 at 22:42, Bryan Lewis <jb...@gmail.com> wrote:
>>
>>> This might be a silly idea, but I'll ask it anyway... Would it be bad to
>>> run a Tapestry application inside Eclipse on a production server? The
>>> objective would be to have full hot-swapping, as I have in my local
>>> development workspace, but maybe it would be bad for memory consumption or
>>> stability.
>>>
>>
>>
>>
>> --
>> Dmitry Gusev
>>
>> AnjLab Team
>> http://anjlab.com
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: running eclipse in production
Posted by Bryan Lewis <jb...@gmail.com>.
Yes, I'm sure that's what he meant. Version 5.3 will turn off live class
reloading in production, which is why he's saying you'll have to run in
development mode.
To clarify my original question (now that it's a dead horse)... I wasn't
worried about reloading of the pages and other top-tier classes. They're
already hot-reloading for me in production if I simply update the .class and
.tml files. (I have the file-check-interval set to 60 seconds.)
But the lower-level classes, not part of Tapestry's domain, don't reload.
For example, I've got business logic in my domain objects, in a lower-level
"model.jar". I've tried running with that jar exploded and updating the
.class files but the changes don't get picked up. The eclipse maven plugin
handles that for me in my development workspace, which is what sparked the
question.
On Mon, Oct 10, 2011 at 11:46 PM, Yohan Yudanara
<yo...@gmail.com>wrote:
> Sorry, but the words "*turns off*" below should be "*turns on*", right?
> Development mode will turn on live class reloading, right?
>
> CMIIW...
>
> On Tue, Oct 11, 2011 at 2:25 AM, Howard Lewis Ship <hl...@gmail.com>
> wrote:
>
> > That would be a very silly idea, and not necessary. If you deploy an
> > exploded WAR (with application class files and resources on the file
> > system, not inside a WAR file) you can get hot swapping (but you'll
> > need to run in development mode in 5.3, which* turns off* live class
> > reloading in production).
> >
> >
>
Re: running eclipse in production
Posted by Yohan Yudanara <yo...@gmail.com>.
Sorry, but the words "*turns off*" below should be "*turns on*", right?
Development mode will turn on live class reloading, right?
CMIIW...
On Tue, Oct 11, 2011 at 2:25 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
> That would be a very silly idea, and not necessary. If you deploy an
> exploded WAR (with application class files and resources on the file
> system, not inside a WAR file) you can get hot swapping (but you'll
> need to run in development mode in 5.3, which* turns off* live class
> reloading in production).
>
>
Re: running eclipse in production
Posted by Howard Lewis Ship <hl...@gmail.com>.
That would be a very silly idea, and not necessary. If you deploy an
exploded WAR (with application class files and resources on the file
system, not inside a WAR file) you can get hot swapping (but you'll
need to run in development mode in 5.3, which turns off live class
reloading in production).
On Mon, Oct 10, 2011 at 12:17 PM, Dmitry Gusev <dm...@gmail.com> wrote:
> Eclipse is not a web container, so you're not running Tapestry in Eclipse
> anyway.
>
> On Mon, Oct 10, 2011 at 22:42, Bryan Lewis <jb...@gmail.com> wrote:
>
>> This might be a silly idea, but I'll ask it anyway... Would it be bad to
>> run a Tapestry application inside Eclipse on a production server? The
>> objective would be to have full hot-swapping, as I have in my local
>> development workspace, but maybe it would be bad for memory consumption or
>> stability.
>>
>
>
>
> --
> Dmitry Gusev
>
> AnjLab Team
> http://anjlab.com
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: running eclipse in production
Posted by Dmitry Gusev <dm...@gmail.com>.
Eclipse is not a web container, so you're not running Tapestry in Eclipse
anyway.
On Mon, Oct 10, 2011 at 22:42, Bryan Lewis <jb...@gmail.com> wrote:
> This might be a silly idea, but I'll ask it anyway... Would it be bad to
> run a Tapestry application inside Eclipse on a production server? The
> objective would be to have full hot-swapping, as I have in my local
> development workspace, but maybe it would be bad for memory consumption or
> stability.
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com