On 28/08/2013 13:00, Remy Maucherat wrote: > On Wed, 2013-07-17 at 14:14 +0000, ma...@apache.org wrote: >> Author: markt >> Date: Wed Jul 17 14:14:28 2013 >> New Revision: 1504148 >> >> URL: http://svn.apache.org/r1504148 >> Log: >> Add the two new resolver types (stream and static) to Jasper in the correct >> order and modify JasperELResolver so the correct resolvers are skipped. > >> - public static ELResolver getDefaultResolver() { >> + public static ELResolver getDefaultResolver(ExpressionFactory factory) { >> if (Constants.IS_SECURITY_ENABLED) { >> CompositeELResolver defaultResolver = new CompositeELResolver(); >> - // TODO ExpressionFactory.getStreamELResolver() >> - // TODO javax.el.StaticFieldResolver >> + defaultResolver.add(factory.getStreamELResolver()); >> + defaultResolver.add(new StaticFieldELResolver()); >> defaultResolver.add(new MapELResolver()); >> defaultResolver.add(new ResourceBundleELResolver()); >> defaultResolver.add(new ListELResolver()); > > I see one issue: in most cases (= no security manager), the static > "cache" resolver instance is used, and it doesn't have the two new > resolvers. The new stream EL resolver for the collections seems to be > more difficult to use with the caching strategy as well, but it looks > possible. > > Ideas ?
I think I have fixed the immediate issue. Do you see any further problems with the new code? Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
