<<Resending..since i wasn't subscribed to the mailing list earlier>>
Hi, I'm trying to use Magnolia as the CMS for an existing struts2 webapp ; since i'm totally new to the CMS world itself, i have some basic questions on the topic. 1. I assume that the jsps created using magnoliaAuthor can be used as-is in the web app ; the <cms:> tags (ie the magnolia provided taglib) will be interpreted by magnolia and <s:> tags by struts, and each of them will ignore the others' tags. 2. Content location : webapp separate from repository -howto?: The jsps will be dynamic in most situations - ex: forms with logic, and will have some static content paragraphs/ images etc. I need the content and images alone to be managed via Magnolia. So, the JSPs/images etc. need to be visible to both the webapp and magnoliaAuthor ; can it be hosted in a single location or should i have copies? 3. web.xml and web app configuration : How does the request get serviced by both the web app and Magnolia ? http://www.mail-archive.com/[email protected]/msg06049.html says "In the JSPs of your action forwards, redirect back to a page managed by Magnolia" - not able to understand how this will work ; my basic assumption is that the *same* page must be handled both by the webapp and Magnolia. 4. Is there an alternate way to access the repository content within the webapp ; ie using standard JSR 170 APIs in the java code and not in JSPs ; for this, i'm thinking the repository could be exported and made part of the webapp ; but not sure if this is a recommended approach. If anyone has any reference/pointers to some intro document that will answer these, it'll be awesome. Thanks! -- View this message in context: http://www.nabble.com/Using-magnolia-with-a-webapp---basics-tp16321435p16321435.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/ ----------------------------------------------------------------
