Hi all,

I just wanted to let you know that I have all the unit tests passing for
using the Merlinized Fulcrum components!  That means that currently in
Turbine 2.4 we are loading the Cache, Crypto, Intake, Localization, Factory,
and Mimetype services as components using Merlin.

This also includes loading components that rely on components.  For
instance, Intake relies on the Localization component loading first.  While
I haven't done much performance testing, things seem very rapid.  And the
additional lifecyle abilities of Merlin over ECM should be worth a lot.

At this point the only big Merlinized Fulcrum component to integrate is the
Factory component.  After that, there are a couple other components we could
integrate including:

Configuration Component
We could leverage Merlin to load up the commons-configuration component
versus doing it manually within Turbine.

Security Component
In Fulcrum is a vastly changed (and I hope improved) security component.
However it does need more work to fit the 'traditional' Turbine model.  I am
thinking that I might just move the current Torque based implementation
which is into /extensions/torque into a project called
/extensions/torque-security and /extensions/ldap-security and only leave the
interfaces in the turbine core.  Then add the appropriate adapters to use
this code with the fulcrum code.  That way existing users can use the
existing torque based security and then be able to migrate to fulcrum
Security if they want.

Scheduler Component
Scheduler seems like it should be screaming out to be a Fulcrum component.
However, I don't use it, I use Jcrontab or Quartz as I don't want the Torque
dependencies.  So, since the torque aspects of it where broken out into a
seperate /extensions project called torque, what I think should be done is
create a /extensions/scheduler project and put all the scheduler code there,
removing all of that from Turbine's core.


Feedback?  Other items for 2.4?  The only other things I can think of is
ditching the TDK and replacing it with the Workflow Example app I wrote for
Fulcrum OSWorkflow that does a good demo of Turbine...

I am hot to get 2.4 done in the next couple months or so.  I am going to be
pushing on finishing Merlin Integration and getting Fulcrum 1.0 releases for
all the components done as soon as possible.

Eric


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to