click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-523) Add a click.xml "deployed" setting.
Date Thu, 09 Apr 2009 14:05:13 GMT


Bob Schellink commented on CLK-523:

Please provide the steps to produce the onDeploy problem as I'm not aware of any issues in
a constrained environment.

Regarding your statement "much faster startup time" can you provide some evidence please.
If resources are already in place Click won't override it so not sure why you see such a massive

> Add a click.xml "deployed" setting.
> -----------------------------------
>                 Key: CLK-523
>                 URL:
>             Project: Click
>          Issue Type: New Feature
>          Components: core
>            Reporter: Adrian A.
> Please add a new setting to click.xml called "deployed", with the default behavior of
false (so that would behave like click is working now).
> When deployed=true, click would not call "onDeploy" methods at all (as it should consider
that everything is in its place in the production system).
> Why would this feature be important?:
> - it would allow Click to run in more restricted environments (like replicated servers)
where writing to files is forbidden 
> - it would be much faster to start (last time I checked, the deploy phase took most of
the time) - this would be important in production mode too, where web application instances
can be hibernated.
> (- with this setting Click could score better in benchmarks compared to other frameworks)
> A simple ANT task could "pre-deploy" everything (e.g. by just starting the application
once locally to have click put it's files where they're needed)  before packaging everything
as a WAR for sending it to the servers.
> Thank you.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message