Boris Kraft 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!

People are turning towards magnolia more and more. And because it's java, also lot of highly skilled developers start to work with magnolia. I think, they all share my problems when I started to work with magnolia. Take the last post of Kyle Gabhart regarding 'New Feature: Publisher role', see http://thread.gmane.org/gmane.comp.cms.magnolia.devel/4269. Those who initially developed magnolia feel comfortable with the magnolia code. Those who try to dig into magnolia would appreciate to have some kind of standardized, and I repeat well-known, proven framework. Instead we need to waste time on a home-grown 'framework' which gets refactored and refactored again. If you have special project requirements and need to extend magnolia it can become a nightmare to keep up with the changes in magnolia.

If you really want the community to boost, maybe you're pov is taken from the wrong side. Shouldn't you take more care about your community, especially about those who potentially take further magnolia: skilled java developers, your community! Not only ask what developers can do for magnolia, also ask what magnolia can do for developers.

Nevertheless, as a user I enjoy magnolia.

--
Cheers,
Michael

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to