Hi folks,
it is time to cut a release for the YAAFI container
fulcrum-interceptor
==========================================================
1) I'm currently refactoring the interceptor support of fulcrum-yaafi to
create a seperate fulcrum-interceptor package. It was a plain mistake to
put the functionality into the container since there is more and complex
code. Adding a dynamic proxy will be done using
org.apache.avalon.framework.service.ServiceManager. This will (in
theory) allow for other Avalon containers oder applications to use the
existing interceptors. I'm actually using them already for another
service framework to identify long running service invocations ... :-)
fulcrum-yaffi
==========================================================
1) I would like to add macro expansion for the
componentConfiguration.xml using a property file to make the
configuration more flexible (i.e. componentConfiguration.properties),
e.g <foo>${my.property}</foo> or
<myWorkDir>${urn:avalon:temp}/work</myWorkDir>
further musings for 1.6
==========================================================
1) The James developers implemented a short code snippet which allows
setter dependency injection instead of ServiceManager lookups. The main
problem is that this feature is not compatible across Avalon containers
and I'm not really keen to implement proprietary extensions. Any
opinions out there if it is worth the effort?
Thanks in advance
Siegfried Goeschl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
