On Fri, 12 Feb 2010 05:22:31 -0200, Igor Drobiazko
<igor.drobia...@gmail.com> wrote:
The value of reloadable service is questionable. If you write tests you
don't have to start the application at all if you are fixing bugs in
services. The cycle of fixing bugs in services is much, much shorter if
you write tests. You change a line of code, click the "Test" button in
your IDE and see the results of the test immediately. You don't have to
switch to
browser, reload the page, etc.
That's the ideal approach. But I think realoadable services still have
their value: when some requirement is changed, the change in code could be
applied to an application in production without restarting the context or
the application. This could be a big plus for high traffic sites. As
Howard says, Tapestry provides dynamic language productivity using a
static typed language. :)
To me, the only absolute truth in software development is that things will
change: changed requirements, changed requirement interpretations, bugs,
laws (at least in Brasil they change a lot), clients opinions, etc.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
