dev@glassfish.java.net

Re: any comparision of deployment option

From: Vince Kraemer <Vince.Kraemer_at_Sun.COM>
Date: Thu, 08 Mar 2007 09:38:46 -0800

ludovic champenois wrote:
>
> 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 [snip]
>> 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.
True. But it would be wasted time, if someone already has that data...

> 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...
Okay... If a user wanted to have a very tight edit/compile/test loop,
they would need to add a wait step between the compile and test...
watch for the status file if they use the 'touch the dot-reload'
strategy [assuming there is a lag in between when the reload file is
touched and when the app is ready to be tested again]
> 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
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>