[jboss-jira] [JBoss JIRA] (WFLY-5542) Look into using apache's upstream JSTL

[ https://issues.jboss.org/browse/WFLY-5542?page=com.atlassian.jira.plugin.... ] Radim Hatlapatka edited comment on WFLY-5542 at 8/18/16 6:53 AM: ----------------------------------------------------------------- I've taken look to some of the differences. Here are some of my findings based on going through the source code diffs (I have been comparing https://svn.apache.org/repos/asf/tomcat/taglibs/standard/trunk in revision {{1756754}} and git@github.com:jboss/jboss-jstl-api_spec.git with latest commit {{ce6adae9663904c958feb856b3c09013c2a2b3da}}): # missing fix in apache's upstream JSTL for https://bugzilla.redhat.com/show_bug.cgi?id=1320747 # in jboss jstl there is org.apache.taglibs.standard.tag.common.sql.DriverManagerAccessor created as hack needed for using DriverManager in modular environment. # secure processing can be configured via property in jboss jstl, in apache's upstream JSTL, it is always enforced The differences above should be checked or added to the apache's upstream JSTL before starting to use it. was (Author: rhatlapa): I've taken look to some of the differences. Here are some of my findings based on going through the source code diffs: # missing fix in apache's upstream JSTL for https://bugzilla.redhat.com/show_bug.cgi?id=1320747 # in jboss jstl there is org.apache.taglibs.standard.tag.common.sql.DriverManagerAccessor created as hack needed for using DriverManager in modular environment. # secure processing can be configured via property in jboss jstl, in apache's upstream JSTL, it is always enforced The differences above should be checked or added to the apache's upstream JSTL before starting to use it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)