First responses from the Apache taglibs-dev mailing list are negative, so never mind on the two classes from the previous email. If someone else on their team changes their mind, then it can be revisited.

I had another thought, although it bothers me to have several ELs in your application. It also requires them to open their architecture elsewhere, so maybe I should stick with a hacked version. Basically the JSTL EL has the concept of implicit objects. Their JSTLVariableResolver gets them from an ImplicitObject class, which has the different maps in a PageContext as properties. It looks like it could be refactored to be more generic and allow install additional implicit objects such as the top of the value stack or the current Action. You would write in JSTL EL for their tags, but have access to Webwork objects. Is it worth pursuing, or is there a better alternative to the JSTL?

Fred.



-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to