Hei på deg :)
I think it was Benjamin Mestrallet (eXo) who said some wize words about
this, something like: Weaving together a Portal (which is pretty much a
CMS implementing portlets) and a CMS leads to a conflict of interest, as
both systems wish to control the view/gui of the content.
The native solution to this problem is of course to negate the CMS's
dealing with the view layer. In effect, this would mean using Magnolia's
content repository (JCR) with a portal system. But I'm sure it would be
possible to implement some of Magnolia's templates as portlets.
I'm not sufficiently comfortable with the Magnolia architecture or the
portlet specification to say which is the most cost-effective approach.
-Ferris
Trond Andersen wrote:
Hello
I've just started looking into Magnolia. Gotten the code up and
running in IntelliJ/Tomcat - so far very good :-)
Then I have a question to people using Magnolia. Our customers usually
have both a Portal product - like BEA portal. In that perspective
there's a need for using a content management system, but this content
management system won't control the layout of the site - this is the
Portal's responsibility. Have anybody tried to combine Magnolia with
for instance BEA Portal or some of the other Portal products (JBoss,
IBM or Oracle)? If so how have you done it? Is it easy to get Magnolia
work in such an environment?
The other perspective that I would like to consider: BEA Portal 8.1
have an API - which is loosely based on the API that became JSR170 -
and if I were to implement an adapter for this BEA spesific API, where
should I start looking? Are there any natural extension points that I
could use?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
