what the recommendations for development are and how to change them.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Live-reload-in-production-tp4313825p5072072.html
Sent from the Tapestry - User mailing list archive at Nabble.com
For 5.4, we can introduce yet another level of indirection that
indicates that live reloading is desired in production mode; perhaps
an enum to define what gets reloaded. Is there a JIRA issue yet?
Thanks Howard - that sounds great.
Created issue:
Any update on this?
We're about to upgrade to T5.3, but conveniently use template reload in
production on rare occasions.
From prior discussions a symbol would/could be introduced, but don't seem
like it has..?
Any way of supporting reload(without production=false)? Or is the dynamic
component
On Mon, Dec 12, 2011 at 1:20 PM, Magnus Kvalheim mag...@kvalheim.dk wrote:
Any update on this?
We're about to upgrade to T5.3, but conveniently use template reload in
production on rare occasions.
From prior discussions a symbol would/could be introduced, but don't seem
like it has..?
Any
On 20.04.2011 21:03, Thiago H. de Paula Figueiredo wrote:
On Wed, 20 Apr 2011 15:21:10 -0300, LLTYK ll...@mailinator.com wrote:
Disabled, so you automatically get better performance. I don't think you
should have to tweak Tapestry options to get better performance.
Good point. But a similar
:
http://tapestry-users.832.n2.nabble.com/Live-reload-in-production-tp6288037p6293772.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional
On Wed, Apr 20, 2011 at 4:07 PM, Howard Lewis Ship hls...@gmail.com wrote:
That's my intention. Live class reloading would be disabled in
production, and enable in development.
I think that is reasonable, but I think it should be treated similar to
tapestry.secure-enabled. By default it is
or needs to be changed i have to create a new version
with the changes and this needs to be re-deployed.
If this is not possible we shutdown the app instead of changing a production
webapp.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Live-reload-in-production
On 19.04.2011 19:11, Howard Lewis Ship wrote:
Out of curiosity ... does anyone out there rely on live class
(template, message catalog, whatever) reloading in their live,
production application? Now, normally, I'd think not, because the
deployed app will be packaged in a WAR and the unit of
On 20.04.2011 01:36, Howard Lewis Ship wrote:
Well, then, you're screwed in Tapestry 5.3 :-) Looks like we'll
Ouch.
How about letting the community vote on this? I would hate to go back to
JSP or PHP.
probably have to introduce a new symbol to allow this to be enabled in
production. But I
On Wed, 20 Apr 2011 06:26:12 -0300, Vangel V. Ajanovski a...@ii.edu.mk
wrote:
On 20.04.2011 01:36, Howard Lewis Ship wrote:
Well, then, you're screwed in Tapestry 5.3 :-) Looks like we'll
Ouch.
How about letting the community vote on this? I would hate to go back to
JSP or PHP.
You can
probably have to introduce a new symbol to allow this to be enabled in
production. But I think the vast majority of deployments will not need
At the very least, can there be a patch that could be applied to 5.3
source on this ?
On Wed, Apr 20, 2011 at 7:56 AM, Thiago H. de Paula
On Wed, Apr 20, 2011 at 1:36 AM, Howard Lewis Ship hls...@gmail.com wrote:
On Tue, Apr 19, 2011 at 4:22 PM, Adam Zimowski zimowsk...@gmail.com wrote:
Excuse me asking, but with class reloading disabled in production,
template reloading still works, correct?
My designer who mostly does TML's
Does anyone out there rely on live class
(template, message catalog, whatever) reloading in their live,
production application?
and what critical benefit does this offer?
I've used live class reloading on a production system a few times, but
it always felt wrong to me. :)
However, keep
On Wed, 20 Apr 2011 13:32:17 -0300, Mark mark-li...@xeric.net wrote:
I understand the problems with giving people too many options.
However it can be really tricky to decide what should be configurable
and what need to be fixed. I wouldn't want to use a word processor
that only allowed me to
What I think should be discussed is what's the best default value for it:
enabled or disabled?
That, to us makes no difference, as long as the option is there in 5.3 :-)
On Wed, Apr 20, 2011 at 12:11 PM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
On Wed, 20 Apr 2011 13:32:17
Disabled, so you automatically get better performance. I don't think you
should have to tweak Tapestry options to get better performance.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Live-reload-in-production-tp6288037p6291747.html
Sent from the Tapestry Users mailing
On Wed, 20 Apr 2011 15:21:10 -0300, LLTYK ll...@mailinator.com wrote:
Disabled, so you automatically get better performance. I don't think you
should have to tweak Tapestry options to get better performance.
Good point. But a similar argument can be used: enabled, so you get a
faster
Good point. But a similar argument can be used: enabled, so you get a faster
development environment without tweaking options. My gosh, these decisions
are hard. :)
Couldn't it be enabled by default in development mode and disabled by
default in production mode? Isn't that how HTTPS and some
On Wed, Apr 20, 2011 at 10:03 PM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
On Wed, 20 Apr 2011 15:21:10 -0300, LLTYK ll...@mailinator.com wrote:
Disabled, so you automatically get better performance. I don't think you
should have to tweak Tapestry options to get better
On Wed, Apr 20, 2011 at 12:37 PM, Mark mark-li...@xeric.net wrote:
Good point. But a similar argument can be used: enabled, so you get a faster
development environment without tweaking options. My gosh, these decisions
are hard. :)
Couldn't it be enabled by default in development mode and
Hi,
In a busy live environment I would prefer disabled by default
but still doable programmatically for occasional critical patching.
This would allow reloading to be hooked for example to some
administrative web service and result in better atomicity if multiple
files need to be patched.
That
Out of curiosity ... does anyone out there rely on live class
(template, message catalog, whatever) reloading in their live,
production application? Now, normally, I'd think not, because the
deployed app will be packaged in a WAR and the unit of redeployment is
the entire WAR ... but I suppose
I'm not using 5.2 yet (sigh), but I do use exploded WARs in deployment.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
On Tue, Apr 19, 2011 at 11:23 AM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
On Tue, 19 Apr 2011 15:21:44 -0300, Howard Lewis Ship hls...@gmail.com
wrote:
On Tue, Apr 19, 2011 at 11:07 AM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
I'm not using 5.2 yet (sigh), but
On Tue, Apr 19, 2011 at 2:53 PM, Howard Lewis Ship hls...@gmail.com wrote:
On Tue, Apr 19, 2011 at 11:23 AM, Thiago H. de Paula Figueiredo
thiag...@gmail.com wrote:
On Tue, 19 Apr 2011 15:21:44 -0300, Howard Lewis Ship hls...@gmail.com
wrote:
On Tue, Apr 19, 2011 at 11:07 AM, Thiago H. de
I never used live reloading in production, but it might be a cool marketing
weapon. We could promote it as seomthing similar to ZeroTurnaround's
LiveRebel:
http://www.zeroturnaround.com/liverebel/
Imagine a new slogan on Tapestry's webpage: With Tapestry you can roll out
and roll back changes to
On Tue, Apr 19, 2011 at 4:00 PM, Igor Drobiazko
igor.drobia...@gmail.com wrote:
I never used live reloading in production, but it might be a cool marketing
weapon. We could promote it as seomthing similar to ZeroTurnaround's
LiveRebel:
http://www.zeroturnaround.com/liverebel/
Imagine a new
Excuse me asking, but with class reloading disabled in production,
template reloading still works, correct?
My designer who mostly does TML's expects templates be reloadable in production.
Adam
PS.
On a side note, what about a hybrid switch? Like component class
reloading but disable service
On Tue, Apr 19, 2011 at 4:22 PM, Adam Zimowski zimowsk...@gmail.com wrote:
Excuse me asking, but with class reloading disabled in production,
template reloading still works, correct?
My designer who mostly does TML's expects templates be reloadable in
production.
Well, then, you're screwed
I think live reload in production is a terrible idea.
Production should be locked down. Even if you are using exploded version of
the application,
the app server should explicitly be told to reload the app, in which case live
reloading is not required.
On Apr 19, 2011, at 7:36 PM, Howard
I plead to ask, if possible to enable a switch for template reloading.
I may be screwed, literally...
Adam
On Tue, Apr 19, 2011 at 6:36 PM, Howard Lewis Ship hls...@gmail.com wrote:
On Tue, Apr 19, 2011 at 4:22 PM, Adam Zimowski zimowsk...@gmail.com wrote:
Excuse me asking, but with class
On Tue, 19 Apr 2011 20:39:46 -0300, Adam Zimowski zimowsk...@gmail.com
wrote:
I plead to ask, if possible to enable a switch for template reloading.
I guess this won't be a problem, as it doesn't touch class
transformations, proxies, etc.
--
Thiago H. de Paula Figueiredo
Independent
Hi Howard,
Maybe the question should really be:
Does anyone out there rely on live class
(template, message catalog, whatever) reloading in their live,
production application?
and what critical benefit does this offer?
I am with you on the paradox of choice. When I roll out new
34 matches
Mail list logo
