On Sat, Jan 3, 2009 at 6:35 AM, Jeromy Evans < jeromy.ev...@blueskyminds.com.au> wrote:
> > I finally made time to convert some 2.1.3-SNAPSHOT applications to the > current trunk (2.1.6-SNAPSHOT). > All use a combination of the REST, Convention (replacing CodeBehind) and > Tiles plugins. > > Result: SUCCESS (eventually). Nice work! > <snip> I've also decided to upgrade our application(s) to 2.1.15 and I've encountered a very weird issue (which, as far as I can remember, was also reported at the mailing list); it seems that there are some problems with libraries (or custom templates). We've been using (a modified version of) tabletags, and since the upgrade to Struts 2.1.15 we had to fix an obvious API change, but we've also encountered an issue with the calling of JSP tags in the freemarker templates. They no longer work out of the box (that is, you now need to import them explicitely - meaning doing an assign foo=JspTagLibs etc, including the JspSupportServlet in web.xml). That's not a problem per se (although it would be nice to allow us to use the previous approach, but I disgress), but the problem is that a registered path does not correctly get found. I had the following line added to our templates: <#assign tt=JspTaglibs["/tabletags"]> And it kept complaining it couldn't find the webapp resource. Curiously enough (after some searching) I found the solution to be to add another taglib with an URL before this import would actually resolve the issue. So I changed the template as follows: <#assign page=JspTaglibs["http://www.opensymphony.com/sitemesh/page";]> <#assign tt=JspTaglibs["/tabletags"]> And strangely enough, it worked fine even though I didn't even use the Sitemesh page taglib anywhere. I'm baffled, to say the least. I'll try to find out if this is a freemarker issue, but I would appreciate anyone else's input as well - obviously. Cheers, Phil -- "We cannot change the cards we are dealt, just how we play the hand." - Randy Pausch
