On 17/06/2013 23:08, jeff_shanho...@mcafee.com wrote: > We have precompiled tags which were compiled under 5.5.35 and don't > work under 7.0.34. From my investigation, it appears it's due to an > interface change in JspSourceDependent. The return type of > getDependants() changed. For us the solution isn't as simple as > recompiling for two reasons: we have shipping products which plug > into our tomcat based platform and some such products target multiple > versions of our platform, some of which are 5.5 based and some are > 7.0 based. > > Is this a bug?
No. > Shouldn't there be backward compatibility for > precompiled tags? No. While we don't break compatibility very often, there is no guarantee of compatibility for pre-compiled tags (or JSPs) even between point releases let alone between releases two major versions apart. Pre-compilation is only supported when performed against the release that that pre-compiled artefacts will be running on. > Is there anything that can be done to get such > existing tags working? > I'm looking for any guidance on how to move > forward in addressing this issue. 5.5.x is no longer supported so that short answer is move all your products to 7.0.x. Over 12 months notice was given for 5.5.x end-of-life so there really is no excuse for not having moved to 7.0.x already. Other options that come to mind: - don't pre-compile the tag files - pre-compile as part of the install procedure rather than at build time - patch Tomcat 5 (that will break any existing pre-compiled tags) - re-write your tag files as tags Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
