Great! One possible issue, and we'll find out in the next day or two is that the Gump build may have used Javamail as an installed package at '1.3" version, so moving to '1.3.1' may cause gump failures. However, if that is true, we should try and get Gump updated.
Also, I wonder if there is some sort of javamail api we could compile against? Eric -----Original Message----- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 3:14 AM To: [email protected] Subject: [Fulcrum] Current State of Fulcrum Hi folks, I just uploaded the new website of Fulcrum (http://jakarta.apache.org/turbine/fulcrum/) with the following changes/improvments YAAFI ========================================================== +) YAAFI and Fulcrum ResourceManager now supports decryption, e.g. running YAAFI with encrypted role configuration file and/or encrypted resources - this might not be for everyone though but is essential for my company to roll out applications without everyone kicking out the licence manager ... :-) +) YAAFI now supports reconfiguraion of service components by exposing a ServiceLifecycleManager +) There is now a ReconfigurationService which uses a background thread to monitor configuration files. If a monitored configuration file changes either the whole container or a list of service components are reconfigured (assuming they implements Reconfigurable). A good (theoretical) example would be the Torque component - changing the database settings enforces a reconfiguration of the Torque service to pickup the new settings. +) The bootstrapping of YAAFI was improved to use a componentConfiguration.xml containg information about the various other configuration files. +) YAAFI now supports running service components making assumptions about the Avalon Context (Phoenix,Fortress,Merlin) but it is not properly tested. +) Improved the documentation Other Services ========================================================== +) I fixed a few role configuration files to declare the role-entries in the correct instantiation order (see changelog). This is a requirement since YAAFI has no metadata to determine the instantiation order automatically. +) Ugrading from javaemail-1.3 to 1.3.1 and Turbine 2.3 to 2.3.1 to improve the dependency convergence report - this just leaves the HSQLDB dependency to be cleaned up Cheers, Siegfried Goeschl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
