[
https://issues.apache.org/jira/browse/PLUTO-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David DeWolf resolved PLUTO-278.
--------------------------------
Resolution: Fixed
I now use an abstract factory to retrieve a evaluator proxy which can handle
the specific environment in which it is deployed. Reflection is used to
determine support. Add apache taglib standard jars to the classpath for
support in < 2.0 containers. 2.1 is not yet support (ELContext), but should be
planned at sometime in 1.2.x.
> Create module pluto-taglib-el
> -----------------------------
>
> Key: PLUTO-278
> URL: https://issues.apache.org/jira/browse/PLUTO-278
> Project: Pluto
> Issue Type: Improvement
> Components: portlet container taglibs
> Affects Versions: unspecified
> Reporter: Daniel Krieg
> Assigned To: David DeWolf
> Priority: Critical
> Fix For: 1.1.1
>
> Attachments: pluto-1.1.0-taglib-el.diff, pluto-1.1.0-taglib-el.diff,
> pluto-taglib-el.tar.gz
>
>
> We must separate EL tags that link against JSP 2.0 from those that do not.
> The EL version of ParamTag currently in SVN is requiring JSP 2.0 JARs thus
> making the entire module unusable in a JSP 1.2 environment like Weblogic 8.1.
> Creating a separate module for the EL tags is therefore manditory. I have
> created and submitted a patch that will make necessary changes to use the
> pluto-taglib-1.1.0-SNAPSHOT.jar usable in Weblogic 8.1.5. We may want to
> also consider 2 versions of the pluto-taglib-el modules, one that links
> against JSP 2.0 and another agains jstl-1.0 and standard-1.0 jars for use in
> JSP 1.2 environments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
