Hi folks,
might be of interest for you - at Jakarta Fulcrum we developed a simple Avalon Container to replace the obsolete ECM and Merlin - YAAFI.
http://jakarta.apache.org/turbine/fulcrum/fulcrum-yaafi/index.html
It is very simple (intentionally) but might fit your needs
+) I already embedded YAAFI into JAMES to provide S/MIME and PDF signature for my company (sorry, this stuff I can't contribute)
+) we currently work on component compatibilty to run a Phoenix or Fortress component within YAAFI
+) we have couple of new service such as Groovy support, encryption/decryption, ...
+) if there is a need I can also commit a couple of components to map event/commands to Groovy scripts
Cheers,
Siegfried Goeschl
-------- Original Message --------
Subject: Plans for Fulcrum release ....
Date: Mon, 14 Feb 2005 11:09:14 +0100
From: Siegfried Goeschl <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Organization: IT20one GmbH
To: turbine-user@jakarta.apache.org, turbine-dev@jakarta.apache.org, [EMAIL PROTECTED]
Hi folks,
within the next 4 weeks I want to cut a new release of Fulcrum for Turbine 2.4.x
RECENT FULCRUM CHANGES ===========================================================
1) there is a new Avalon container called YAAFI (Yet Another Avalon Framework Implementation) to run the existing Fulcrum services. YAAFI is light-weight Avalon container to be embedded in other applications and comes with litte baggage in terms of dependencies. It is intended as replacement for the depecated ECM and Merlin Container.
2) Fulcrum HsqlDB Service to embed a HQSLDB server in your application
3) Fulcrum ResouceManager Service - a facade for accessing resources currently file system
4) Fulcrum Groovy Service - allows execution of Groovy scripts with access to the Avalon infrastructure
PENDING FULCRUM CHANGES (NOT COMMITTED YET) ===========================================================
1) YAAFI improvements
1.1) improved bootstrapping of YAAFI
1.2) transparent decryption of configuration files based on JCA/JCE
1.3) support for <component-type> to specify the container type to be expected by the component. This allows for reuse of existing services written for Excalibur, Phoenix or Fortress
1.4) support for <container-type> to allow YAAFI to be embedded in a Fortress or Phoenix container, e.g. JAMES
2) Fulcrum PBE Service provides a service for Password Based Encryption based on PBEWithMD5AndDES/PBEWithMD5AndTripleDES.
3) Fulcrum XSLT Service - intgration with DOM4J and Fulcrum ResouceManager Service. This improved service will not be backward compatible
4) I'm tinkering with automatic reconfiguration of YAAFI using a dedicated Fulcrum Reconfiguration Service. This service would monitor the componentConfiguration.xml and reconfigure YAAFI if the file has changed. This allows automatic reconfiguration without any client/server communication
5) a Turbine YAFFI Component Service to bootstrap YAAFI within a Turbine application
6) Fulcrum ResourceManager Service provides transparent encryption/decryption of resources.
REQUEST FOR HELP ===========================================================
1) Help from the Excalibur community would be greatly appreciated to kickstart component compatibilty testing
2) Any who would like to work on bleeding-edge Fulcrum/Turbine?!
Thanks in advance
Siegfried Goeschl
