Backward compatibility is not the only one issue. Think of new users who are experimenting with Tapestry. If everything is realodable per default, it is very likely that they app will be broken. They will write some package private methods and experience errors which are very hard to understand. After that they will be annoyed and say that Tapestry is broken and bad. Do we really want it?
On Thu, Aug 12, 2010 at 8:45 AM, Dmitry Gusev <[email protected]>wrote: > I agree about backward compatibility, but introducing new features disabled > by default may cause that nobody will use those features even in new > applications. > I like the idea to analyze if service can be made reloadable in runtime and > log warning if it doesn't. This won't break compatibility but give new > projects chance to use live class reloading without additional > configuration. > > On Thu, Aug 12, 2010 at 09:55, Igor Drobiazko <[email protected] > >wrote: > > > For backward compatibility reasons it should be enableReloading() and not > > preventReloading(). Otherwise the most apps will suffer from this issue. > Do > > you remember our promise? Making new features (that can break my app) > > configurable and disabling them per default is a good practise. > > > > > > On Thu, Aug 12, 2010 at 1:01 AM, Robert Zeigler <[email protected]> > > wrote: > > > > > Does: > > > binder.bind(Interface.class, Implementation.class).preventReloading(); > > > > > > not do the trick? > > > > > > It's already disabled for services that use buildXXX since Tapestry > won't > > > know the implementation class of the service. > > > > > > Robert > > > > > > On Aug 11, 2010, at 8/115:40 PM , Thiago H. de Paula Figueiredo wrote: > > > > > > > On Wed, 11 Aug 2010 19:18:42 -0300, Igor Drobiazko < > > > [email protected]> wrote: > > > > > > > >> But you would recreate only those services that you need right now. > > All > > > >> other "heavy" services are created later on demand. > > > > > > > > These heavy service methods could be invoked by the recreated > services, > > > but I agree with you too. > > > > > > > > By the way, I couldn't find any way of disabling the services live > > > reloading. Is there any? If not, it would be nice to have one. > > > > > > > > -- > > > > 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 > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > -- > > Best regards, > > > > Igor Drobiazko > > http://tapestry5.de > > > > > > -- > Dmitry Gusev > > AnjLab Team > http://anjlab.com > -- Best regards, Igor Drobiazko http://tapestry5.de
