Hi Matteo,

thank you very much for your soon reply.
It was helpfull.
So first I will try to learn as much as I can about Magnolia.
Than If I will have some questions I will write back to forum.

I wrote this article because I was not sure if Magnolia is right way for me.
As you write that it is possible to use Magnolia in my way (depend on my
requirements) I
will learn more.

Thanks again.

Jason Smith


Matteo Pelucco (Tinext) wrote:
> 
> 
> On 28.07.2010 21:57, Jason Smith wrote:
>> Hi all,
> 
> Hi, Jason
> 
>> I try to solve problem with integration some CMS to existing web app.
>> Web app is based on java (basic 3-layered architecture). UI layer is
>> based on
>> Apache Wicket framework.
>> Our web app is deployed on Glassfish server.
>>
>> I need to put a new parts to my existing pages, it will be CMS part.
> 
> Ok, so, if I right understand, you need to integrate Magnolia into your 
> existing webapp, and not viceversa, isn't it?
> 
>>
>> For example:
>> I have two divs on web page.
>> Whole page html is generated by wicket.
>> First div is generated by wicket with data from service.
>> Second div - CMS div is generated from csm. My idea is to ask CMS
>> for appropriate particional HTML for CMS element.
> 
> Yes, it seems so.
> Is it of course possible. You can interact whith Magnolia in a 
> "REST-like" way, because each portion of a web page generated by 
> Magnolia can be called as single "atoms".
> 
> A page in Magnolia is often built with paragraphs.
> You can call pages
> 
> e.g.: http://yourhost/yourPage.html
> 
> or you can call also paragraphs
> 
> e.g.: http://yourhost/yourPage/pageArea/pageParagraphX.html
> 
> Each call respect the MVC Magnolia framework 
> (ParagraphRenderer/TemplateRenderer + JCR data + Freemarker)
> 
> Otherwise, you can customize Magnolia filters to fulfill you requirement.
> 
>> But it is only my idea.
>>
>> Do you thing that Magnolia CMS is good for my case.
>> If yes can you give me some tips how to do that, because
>> i really don't know how to do it.
> 
> First, learn as much as you can about Magnolia and STK.
> You can find url in last days messages in this list.
> 
> Then, you have to choose your approach.
> A REST approach (easy)
> A webservice approach (mor complicated)
> A custom approach (it depends :-))
> An include approach, where you place Magnolia aside you existing webapp 
> (i don't know..)
> ...
> 
> 
> HTH,
> Matteo
> 
> 
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
> 
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Magnolia-to-existing-web-app-integration-question-tp29290379p29295072.html
Sent from the Magnolia - User mailing list archive at Nabble.com.


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to