click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Schellink <>
Subject Re: Issues or no issue...
Date Tue, 15 Jun 2010 12:28:37 GMT
I still don't see use cases covered by onDeploy that is not covered by the Servlet3.0 approach?
components have up to 20 resources including images,CSS and JS. That is a lot of resources
that has
to be managed by onDeploy.


On 15/06/2010 22:17, Adrian A. wrote:
> IMHO onDeploy should not be deprecated, as it's a smart approach for the
> components to be "aware" and
> handle their own resources in a pretty "independent manner": not many
> other frameworks have this feature - even worse for most other: the user
> has to take manually care of the resources.
> For development mode, or "very dynamic" applications, it's very nice
> that the Component can take care of itself :)
> Of course, maybe onDeploy + getHeadElements could be further improved to
> reduce code duplication, or maybe there's a better approach, but IMHO
> onDeploy is just a too nice feature of Click to deprecate it.
> Adrian.

View raw message