On 6/5/07, Bernd Fondermann <[EMAIL PROTECTED]> wrote:
Stefano Bagnara wrote:
> Bernd Fondermann ha scritto:
>> Stefano Bagnara wrote:
>>> While I think that a spring class to read the avalon descriptor is cool
>>> I also think it has a couple of drawbacks to take into consideration:
>>>
>>> 1) the avalon descriptor is in the phoenix function: in the current ant
>>> build you cannot make a function to depend on another functions. Maybe
>>> Robert has a solution for this.
>> I will base the work on
>>
https://svn.apache.org/repos/asf/james/server/trunk/phoenix-deployment/src/conf/james-assembly.xml
>>
>> We could easily move that into a generic conf module or so, if needed.
>
> In future we'll probably split service classes from their own avalon
> wrappers. In that eventuality we'll have to point Avalonized wrappers in
> the assembly and POJOs in the spring xml.
I tried this approach and to get there will take quite some effort ;-)
it will but it can be done per module/ for some modules (IMAP, say)
the code is very easy to fix. for others, it is more difficult.
i've been thinking about logging for a while. ATM JAMES is strongly
coupled to avalon through logging. i wonder whether (byte) code
weaving might be the best way to decouple this dependency.
> Btw I see your "current proposal" more as a cool spring based avalon
> container. So a replacement for Phoenix, while sticking to avalon.
Interesting observation.
In fact, currently, we are so heavily dependent on Avalon/Phoenix, that
Spring acts as a container-container.
interesting
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
