Not sure if this would work, but try placing the struts2 jar file in jboss-web.deployer or jboss-web.deployer/jsf-libs (possibly in addition to having it at server/xxx/lib).
If that doesn't work, looks like you will be stuck placing it into web-inf/lib.
Thanks for the reply, Peter.
I'm working in an enterprise environment, so we're not supposed to be touching the jboss-web.deployer directory.
What I'm trying to get a feel for is, what determines where JBoss will search for the TLD file. Is there a setting for the server, something for web.xml, an environment variable (CLASSPATH?) that determines where it will look, or is it just always looking in the jboss-web.deployer directory and nowhere else?
As far as I know, the only place where TLDs are looked for is WEB-INF/lib. Because the log entries you posted showed that the jboss-web.deployer was also being scanned (which makes sense because that is where the JSP-related TLDs reside) I suggested placing the JARs there. I know of no setting where you could specify a "tldpath". Obviously the standard class locations are not checked of it would have found the TLD in the jar in the server/xxx/lib directory.
Have you fixed this issue?...please let me know. Thanks