You could write some components against the JCR API and access the underlying repository Magnolia uses (I don't know if this is possible with OpenCms). Have a look at the Jackrabbit website (that's the repository implementation Magnolia uses) to learn how to register the repository with JNDI. Then just configure Magnolia to use that one instead of the preconfigured location. Afterwards you are able to also access the repository from your tapestry webapp with a JNDI lookup. This approach has some security flaws though. Magnolia has its own security checks and connects to the repository through just one user. If you access the repository directly you bypass Magnolias security layer. The Jackrabbit website shows how to register the repository with JNDI in the local web context. So you only have access to the repository in the context where you registered it. In order to have your Tapestry app and Magnolia live in different contexts and still access the same repository you will have to register it globally thus making it available to ALL contexts in your container. In combination with the above mentioned this can have serious impacts on security. So be careful what you do.

Cheers,

Uli

unimatrixzero schrieb:
Hi!

I'm currently testing a few Open Source WCMS Systems like OpenCms and
Magnolia (Java based).
All this WCMS using JSP's for Templates (together with a own Taglib) and
Magnolia stores the Content
in an JSR-170 Java Content Repository. I'm wondering if it is possible to
integrate some Content
from this Content Management System into a Tapestry Application. Goal would
be that the user
is able to modify content in the Content Management System (like writing an
article or adding a picture)
and this content could be then included in Tapestry. Is this in some way
possible?
One of the greatest problems is that Tapestry uses his own kind of templates
and OpenCms and Magnolia the JSP ones.
Do you think there is a way to integrate this two things?

Maybe you could help me.
Thank you in advance.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to