On 13.10.2005, at 00:42, Kyle Gabhart wrote:
You are correct, the level of effort would be substantial, but I can
easily envision a Magnolia 3.0 release with a revised Spring-enabled
Ioc/AOP architecture that provides a truly flexible, lightweight
solution that can be deployed into any J2EE server environment and
easily wired up to leverage different datasources, transaction
engines, JCR implementations, logging frameworks, security mechanisms,
etc..
That sounds great, but why would I want to do that? Flexibility and
Comfort are opposite characteristics, no? To take your idea one step
further: why not provide an XML transformer as the sole core of
Magnolia and everything else is defined in XML and XSL? Remember:
everything in life is a transformation. Ultimate flexibility!
Super-lightweight! Totally unusable!
The goals of magnolia have always been these two:
1) make it easy (to use, implement, deploy ...)
2) keep to standards where sensible
It doesn't rule out cool stuff like Spring, but just because XYZ is the
hot acronym (or technology) of the moment means it is true to
Magnolia's philosophy.
Keep up the discussion!
- Boris
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
