Bernd Fondermann wrote:
wouldn't it be best to POJO-fy _first_ without a specific container in
mind (a larger task on its own) and then afterwards look at all the
mature containers to integrate with?
My thoughts exactly. IMHO, if the container makes you do weird things
with your design at the start, then it's not a good container.
for example the parent class hiearchie for core components like
org.apache.james.James is based on classes like
org.apache.avalon.framework.logger.LogEnabled.
IMHO, to put it politely, yuck. This is an example of why container
software should not be so invasive in your code. To be sure Avalon was
on the cutting edge and investigated a lot of good ideas. I think that
we've learned a bit since then.
LogEnabled provides functionality for what is called an 'aspect'
today. modern IoC frameworks weave those aspects into the components
by 'crosscutting' them - the component has no direct notion of it
happening.
this and similar refactoring steps would make James components much
more POJOs and thus more easily portable into new containers.
I am of the same opinion.
Regards,
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
