<taglib>
<taglib-uri>/tags/struts-bean</taglib-uri>
<taglib-location>/WEB-INF/struts-bean.tld</taglib-location>
</taglib>However, since the tlds are now in the taglib jar we need to change how this works. One way would be to remove the taglib declarations; but this would require changing the JSPs to use the absolute URI. Optionally, you can specify a jar file in the taglib location; however, I do not know if you can refer to a specific TLD in that jar?
Joe Germuska wrote:
At 10:23 PM -0500 2/4/05, Bill Siggelkow wrote:
After deploying then struts-mailreader app, built with maven, the /WEB-INF/struts-logic.tld could not be found. In fact, neither the built 'struts-mailreader' directory or war file contained any of the struts-taglib tlds; but the struts-taglib.jar file was included in the WEB-INF/lib. Perhaps we should change the mailreader app so the TLDs can be pulled from the jar. (Coincidentally, the TLDs are not be included in the struts-taglib.jar)
I think that the TLD issue is now fixed; the base XML files which are transformed into TLDs and the maven.xml file which adds that to the "jar" goal hadn't been copied from the core to the taglib project.
I haven't tested the artifact generated, but I did look to see the TLDs in there, and since I just moved things around, I'm hoping it's all good. I'm also hoping to actually test it this weekend anyway ;-) but I thought I'd mention the fix now...
Thanks for catching this!
Joe
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
