Hi,
(1) as far as I can see, the archetype trunk (turbine-webapp-4.0) points
to Version 4.0-M2.
Should we release it now or wait for Turbine 4.0 Final Release? It seems
quite ready to be used. Nonetheless some testing and validating should be
done.
If we proceed to 4.0-SNAPSHOT changing e.g. of turbine-pipeline.xml would
be required, which is not (yet) backward-compatible.
(2) When looking a little deeper into how actually things are to be
implemented, some questions arise, e.g. how are the security services
considered to be used? For example there exists a class in Turbine called
org.apache.turbine.services.security.DefaultSecurityService
and another class in Fulcrum Security
org.apache.fulcrum.security.BaseSecurityService
and furthermore a (deprecated?) Turbine Adapters in Fulcrum Security
org.apache.fulcrum.security.adapter.turbine.SecurityServiceAdapter
Which of them is needed in which case (or could be substituted), which are
deprecated?
Migrating to Turbine M2 (with Torque OM), probably many things just
continue to work, but what exactly should be dome could be made more
apparent. Especially getting an instance of and saving a user I see more
than one way to do it (I will document this somewhere).
May be the easiest to answer is, when starting a brand-new Turbine project
using Torque what is the way to go. The new Fulcrum Security Torque
persistence managers seem to be the candidate in the first place or not?
So, I think some more explanation is needed at some place ..
Best regards, Georg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
