Hi,

My name is Henrik and I'm a Java consultant working in Sweden. I'm currently looking for a content management system with the ability to integrate with an existing application for a customer. Today the customer has an application written in Java and EJB3 running on a JBoss AS. This is being fronted by a Struts web application. Content is today syndicated from a CMS via RSS into the web application but we don't find this an ultimate solution.

Neither me nor the customer is super happy about using neither Struts nor the current CMS (a nice CMS but written in C++ and CGI) so we are now scanning the market for better suited systems. The thing and the key reason to why I'm writing is, I'm really strugeling in finding the way of how the integration part really should be done.

Let's say I chose Magnolia. How can one integrate the created Magnolia content with the application. Or perhaps better put, is it possible to combine Magnolia with another view technology, like Wicket? Have anyone done this? If not, is there any instructions somewhere of how to implement a Templating Plugin that could used for Wicket? Or is it possible to dispatch a request and include Magnolia content into Wicket like this:

http://herebebeasties.com/2007-03-01/jsp-and-wicket-sitting-in-a-tree/ <http://herebebeasties.com/2007-03-01/jsp-and-wicket-sitting-in-a-tree/>

Perhaps I should use the JCR API, but I'm having a hard time realizing this. It seems like quite a lot of work? What I'm trying to achieve is having the content created by Magnolia but read in separate parts / chunks (like a news paragraph, a page header, navigation elements, etc) by the web application. I presume the web tier is where to call the repository from, right? Honestly, I think there are too few clear examples and discussions about this "out there".

Do you have any suggestions? Thanks a lot, in advance!

Best Regards! /Henrik

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------

Reply via email to