Considering I so far have spent;
4 hours trying to understand Avalon & Phoenix concepts.
1 day applying that knowledge into a functional SAR
1 day to get the existing application running
it is not bad at all. Very happy with the Avalon project, IMHO the best
structured (code-wise) OSS project I have ever seen. I will enjoy this.
I have just managed to apply a ProductDir via the BlockContext (thanks Paul)
and have migrated the previous projects.list (textfile) into the config.xml
instead (Well balanced config system I must say).
Also, manage to make the old service loader functional inside Avalon (for
compatibility), and refactored and an ancient ugly static class, which is
center for a lot of activity, from >2000 lines to about 30, without breaking
compatibility.
Things are moving very smoothly, and I think the first phase (got the whole
old app to run inside Phoenix) will be completed by Monday.
Second phase, will be the Avalonization of existing pieces. That will probably
take quite a long time (>500 of them I think)...
Niclas
On Thursday 13 March 2003 15:13, Paul Hammant wrote:
> Niclas,
>
> Perfect! Rejavanating legacy Java. I've witnessed the same in a big
> Oil company recently. It was a really great project that the company
> was over the moon about in terms of the stabilisation of the product.
> We also tested all of the services as part of the project and shifted
> completely to Test-Driven-Design.
>
> We had different build targets to make SARs for different destinations.
> 'deploy-local' for the local phoenix, 'deploy-live' for the live one.
> Each uses differenr properties (however you want to configure that) and
> had diff config.xml...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
