Cordialement, Christian Mennequin Barclays IRCB / DI 183 avenue Daumesnil 75575 Paris Cedex 12 Phone : 0033 (0)1.55.78.43.05 Email : [EMAIL PROTECTED]
"Leon Rosenberg" <[EMAIL PROTECTED]> 09/01/2007 23:51 Veuillez répondre à "Tomcat Users List" <users@tomcat.apache.org> A "Tomcat Users List" <users@tomcat.apache.org> cc Objet Re: Best way to include common html Is there actually any real requirements for those html-code portions to be outside of the webapp? If no - move them into the webapp :-) If no - write a custom tag which caches the files via normal FileSystem read and dumps them out in the jsp buffer (of course its better to have a class that caches the binaries and the tags only gets the data from this class, but you haven't asked for details, right?) regards Leon On 1/9/07, Scott Cowley <[EMAIL PROTECTED]> wrote: > The problem is that I can't reference JSP includes from app code if the > included file is outside the app's root. > (At least with the default installation of Tomcat). > > -----Original Message----- > From: Scott Purcell [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 09, 2007 1:24 PM > To: Tomcat Users List > Subject: RE: Best way to include common html > > Possibly a framework for templating. Tiles, SiteMesh they are created > for exactly what you are looking for. Of course you can use JSP includes > ... but the frameworks do a better job IMOHO. > > > > -----Original Message----- > From: Scott Cowley [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 09, 2007 2:14 PM > To: Tomcat Users List > Subject: Best way to include common html > > > What is the best approach to get shared HTML files, (such as header and > footer files) located outside each appBase, > included into an application (.jsp) under Tomcat? > > SSI filter ? > Or some context resource setting ? > > Thanks for any help. > > - s.c., university of utah > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ce courriel et ses éventuelles pièces attachées sont confidentiels et ne concernent que le destinataire. Si vous nêtes pas le destinataire ou si vous lavez reçu par erreur, informez en immédiatement lémetteur, effacez le de votre ordinateur et nen faites aucune copie ni diffusion. Ceci sapplique à tout ou partie du document ainsi quaux pièces attachées. La communication à travers le réseau Internet ne présente aucune garantie de sécurité ni de protection contre les virus. Le groupe Barclays nest pas responsable en cas de perte résultant de laction dun tiers par des accès non autorisés, par des interventions sur les moyens de communication ou par la transmission de virus. Barclays se réserve un droit de surveillance sur les réponses qui pourront être faites à ce message. Toute information ou opinion, contenue dans ce courriel ou dans ses pièces attachées, qui serait sans rapport avec lactivité commerciale du groupe Barclays doit être considérée comme personnelle à lémetteur et nengage en aucune façon le groupe Barclays.
