Question on the packaging of tag libraries

2004-03-11 Thread Faine, Mark
Tomcat 4.1.27 on Solaris 8
 
I'm looking at centralizing our tag libraries that our used by several web
applications.  Unfortunately the way one of our vendors packages their
taglibs is not very portable.  I know class files for taglibs can (and
should) go in a jar file and be loaded by the web app from a lib directory
but what about tlds can they also be placed in some central location and
loaded by every web application instead of having to maintain them in each
web application individually.
 
Thanks,
-Mark


RE: Question on the packaging of tag libraries

2004-03-11 Thread Edson Alves Pereira
Maybe this helps.

The required extensions for a tag file are .tag if you write the file in JSP
syntax, and .tagx if the file is only composed of XML elements. The JSP 2.0
specification requires you to place the tag file in the WEB-INF/tags
directory, or a subdirectory thereof. If you want to package the tag file in
a Java Archive .jar file as part of a custom tag library, then you can store
it in META-INF/tags (or a subdirectory of META-INF/tags), and then describe
the tag file in a Tag Library Descriptor (TLD), a type of configuration
file. You do not have to describe the tag files that are placed beneath
WEB-INF/tags in a TLD, but you can, if you want to consolidate a library of
traditional custom tags and tag files in one TLD.

 --
 De:   Faine, Mark[SMTP:[EMAIL PROTECTED]
 Responder:Tomcat Users List
 Enviada:  quinta-feira, 11 de março de 2004 10:38
 Para: '[EMAIL PROTECTED]'
 Assunto:  Question on the packaging of tag libraries
 
 Tomcat 4.1.27 on Solaris 8
  
 I'm looking at centralizing our tag libraries that our used by several web
 applications.  Unfortunately the way one of our vendors packages their
 taglibs is not very portable.  I know class files for taglibs can (and
 should) go in a jar file and be loaded by the web app from a lib directory
 but what about tlds can they also be placed in some central location and
 loaded by every web application instead of having to maintain them in each
 web application individually.
  
 Thanks,
 -Mark