Thanks for the suggestion, but I may not have been clear about what I am trying to do.
I am trying to get away from using JSP, so something like .esp (javascript) works well, but I had trouble getting Magnolia to tolerate the sling:resourceType meta data, so I am back to using JSP for now... Thanks Tyson -----Original Message----- From: Torgeir Veimo [mailto:[email protected]] Sent: Thursday, February 12, 2009 3:23 PM To: [email protected] Subject: Re: tomcat + JNDI + sling 3 On 12 Feb 2009, at 03:27, Tyson Norris wrote: > [...] > However, the templating system (of Magnolia 3.6 - I will mention 4.0 > later) is based on JSPs that must be managed via filesystem > deployment. > Please let me know if you have comments/suggestions on this approach. Did you look into the file system provider for Sling? It allows resources to be located on disk and thus would allow legacy support for JSPs stored as files through slings JSP support. -- Torgeir Veimo [email protected] -------------------------------------------------------------------- This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this email or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you have received this email in error, please immediately notify us by calling our Help Desk at (415) 581-5552 or by e-mailing us at [email protected].
