On Mar 8, 2007, at 8:14 AM, vince kraemer wrote:
> Hi,
>
> I am working on some optimizations for the NB user experience for
> developing enterprise components and apps. I think they will
> depend the deploydir functionality and the use of the dot-reload
> file... But I have to wonder: Is using the dot-reload file to
> trigger an autodeploy really faster when you redeploy a large app.
>
> Is there any comparison out there between using 'deploydir with dot-
> reload' vs. repeated deploydir operations?
>
> I can think of one disadvantage of using the dot-reload
> functionality... The user doesn't get any feedback on when the
> 'redeploy' is DONE. This delay may be significant for enterprise
> scale applications...
>
> Folks may wonder what I mean by 'enterprise scale'. I think the
> Liferay portal is an enterprise scale application (in either of its
> two forms), about 62 MB (ear) or 52.7 MB (war). It may be a bit
> extreme, though.
>
I am not sure our perf team measured this....
Would not be too hard for you, assuming you played with this real app
to try different repetitive deployments (dirdeploy or dotreload)by
changing a simpl jps or class and measure to determine the best option.
For the status of dotreload, I think a file containing the status
(fail or success) is created on disk.Not sure if it is in the file
content of the filename...
Ludo
> Thanks,
> vbk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>