Investigate options for avoiding embedded copy of Spring taglib TLD
Basics
Logistics
Basics
Logistics
Description
We have a copy of Spring’s taglib in our WEB-INF in idp-war and so far I can’t come up with a syntax for referencing Spring’s copy in their webmvc jar. Has to be a way, but if the way is “declare in web.xml” that’s probably even worse given that it hasn’t really changed at all anyway.
Environment
None
Activity
Scott Cantor
June 14, 2023 at 12:24 PM
It hadn’t changed between at least Spring 4 and 6, and I don’t think they care about JSP anymore, so I don’t think it’s worth complicating our lives to fix this, it’s just somethiing I wanted to verify before giving up. I’m not going to diverge web.xml just to fix this since it would break upgrades.
Rod Widdowson
June 14, 2023 at 9:57 AM
I see the problem. ugh.
The silver bullet with all this stuff is to “fix it in the installer”. Almost by definition an installer is a series of ad-hoc kludges to make different visions of reality is work together. (aside: which is why I dislike working on them
Its seems like this might be a better bet than keeping code working in lock step.
We have a copy of Spring’s taglib in our WEB-INF in idp-war and so far I can’t come up with a syntax for referencing Spring’s copy in their webmvc jar. Has to be a way, but if the way is “declare in web.xml” that’s probably even worse given that it hasn’t really changed at all anyway.