incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "LOMBART Christophe" <>
Subject RE: Why not using Magnolia
Date Fri, 18 Mar 2005 10:00:38 GMT
I saw your jetspeed demo and it seems to be very good.
Is it possible to see the code used for this demo ? 

We should definetly see what we have in common. Can you present Graffito to the Magnolia community
? Of course, The Magnolia community is welcome here.
I'm sure Magnilia & Graffito will have too many common points.

Now, how will start this discussion,  ... ? 

I can review the architecture info on Graffito and gives more detail. By this you will have
more technical details. 


-----Original Message-----
From:	Michael Aemisegger []
Sent:	Fri 3/18/2005 10:31 AM
Subject:	Why not using Magnolia
Dear list

I hope you don't mind bothering you with this question again. I've read the 
thread about Lenya and haven't found arguments that would counteract Magnolia. 
Why not using Magnolia?

Let me put it short. Magnolia is a J2EE compliant, open source CMS, see

Magnolia is JCR 170 compliant since the birth of the project in 2003 (first 
slide, now jackrabbit). It has a very nice user interface and a constantly 
growing user and developer community. And it can be combined with Jetspeed. I 
did integrate Jetspeed 1.4 with Magnolia 2. See > Produkt > 
Demo for a demo site. I planned to migrate to Jetspeed 2 as soon as Jetspeed 2 
is production ready.

I might be interested in participating in the project and contribute work, code 
or experience (well, if needed at all).

I can't tell for sure whether the licenses of Apache and Magnolia can go 
together. I don't know whether you are interested in using an existing 
codebase. I cannot tell for sure if the Magnolia community would welcome the 
Graffito project. But I am sure, that the two projects could gain from 
eachother. Magnolia could be the CMS part for administering content, Jetspeed 
could be the presentation and business logic part and Graffito would enrich 
those two with ready to use JSR-168 compliant mini applications.


  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message