[opencms-dev] Opencms Menu share

[Padilla, Patricia]

We did something similar for one of our customers, the customer's website navigation, the site was running in OpenCms, had to be used across various existing applications. In our case, the menu needed to be included in a .js file. Our approach was to create a custom class in OpenCms that built the menu and generated the .js file. In the existing applications we set the "<script src='http://www.someopencmssite.com/sites/default/script/menudata.js> to the absolute url of the .js file generated by OpenCms.  There may be a better approach, but that worked for us.

Patricia  Padilla
Applications Developer


-----Original Message-----
From: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] On Behalf Of Faisal Irfan
Sent: Wednesday, June 29, 2011 12:46 PM
To: opencms-dev at opencms.org
Subject: [opencms-dev] Opencms Menu share

Hello!
     I am new to opencms and have to move our existing application to OpenCms, as our existing Application is huge and is using lot of technologies, so we decided to divide this process in and initially just static pages are going to be generated using opencms and rest will be handled by existing application, so we are now running Opencms and the existing applcation parallel (tomcat context share), issue is that we want whole menu management to be done by opencms .i.e. both applications will be using same menu generated by opencms, any help regarding this, please?


--
Regards

FIrfan




_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/mailman/listinfo/opencms-dev

This email is confidential and intended solely for the use of the individual(s) to whom it is addressed. The information contained in this message may be privileged and confidential and protected from disclosure.

If you are not the author's intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error please delete all copies, both electronic and printed, and contact the author immediately.