Is there anyupdate on the TLD issue? is is being tracked in jira anywhere? There are a few ways of getting around it right now, but they are a pain. - getting the actual location of where the webapp is deployed and copying the file across. Finding the actual file location is a big pain requiring many levels of hacks. - manipulating the web.xml metadata (easily done with a deployer) to redefine the JspServlet. This will override the JspServlet setting in jboss-web.deployer/web.xml (the shared web.xml file for all webapps). By setting a properly formatted <init-param> for the JspServlet you can make it add any tld from any specified jar with no requirements on it existing in the WEB-INF directory of your webapp. | <init-param> | <description>JSTL standard tlds</description> | <param-name>tagLibJar2</param-name> | <param-value>../location-to-jar/jar-containing-tld.jar</param-value> | </init-param> | The problem here is that it does change the global JspServlet setting and all webapps will be able to find your tlds. And its probably not the safest operation to be overwriting the JspServlet like this, but it is possible. It would be a lot easier if this default global web.xml was being handled by deployers and was being exported as an attachment that other deployers could use (like the current MergedJBossWebMetaDataDeployer). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227616#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...