Jason van Zyl <[EMAIL PROTECTED]> writes:
>Hokay. I imagine anyone using Fulcrum can fend for themselves and for
>current users the existing coupled code is the behaviour they will be
>expecting so we can use the couple services. Fun fun! Deja vous!
Please, the code in Fulcrum is much more cleaned up in some respects
(e.g. the organization of the security stuff in fulcrum.security and
then entity / util) instead of putting this all over the place in
utils and om just like the coupled Turbine services.
I'd like to keep the organization of the Fulcrum services intact so
just taking the Turbine coupled services, replace turbine.services
with fulcrum in the package names and adding lifecycle interfaces
would kill much of the work that was already done on the first
turbine -> fulcrum migration.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
