| Re: [jsp-dev] Property to Enable Older Sun URIs In JSTL 3.0 |
Hello again,
Following up, as I thought about the TLD processing more, I think, if any property should exist, it should be handled by JSP Implementation instead.
As for JSTL, the question is whether we should have backward compatibility with the http://java.sun.com/jsp/jstl/* URIs or not. If so, the only option I see now is to add another set of TLDs (that use the older URIs). JSP would scan the TLDs, and then both the older and newer URIs could be used automatically.
Volodymyr
Hi,Volodymyr
I was thinking this property would be JSTL implementation-specific, but we can add it to the JSTL API/Spec if preferred.
Although, since you mention it, I suppose it could be implemented through a JSP implementation? That could be better, potentially.On Wed, Dec 22, 2021 at 4:08 PM Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx> wrote:I don't see JSP the spec or api being concerned about this.Seems like something a JSP implementation, like Jakarta WASP (used in Glassfish) or Apache Jasper (used in Jetty and Tomcat) would implement.- Joakim_______________________________________________On Wed, Dec 22, 2021 at 3:04 PM Volodymyr Siedlecki <volosied@xxxxxxxxx> wrote:_______________________________________________Hello,For the JSTL 3.0 release, will change the default Taglib URIs to jakarta.tags.*. However, for application compatibility, we plan to include a property to switch to the older tags URIs (which will be deprecated and removed in later releases).
I would like to get feedback on this property name. Currently, I propose to create org.eclipse.useSunURIs as a context parameter?
If you have other proposals or comments, please reply or comment in https://github.com/eclipse-ee4j/jstl-api/issues/193
Thanks,Volodymyr
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev
jsp-dev mailing list
jsp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jsp-dev