You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "David H. DeWolf" <dd...@apache.org> on 2005/09/01 05:40:54 UTC
Re: EL support in PortletParam
The specification does not mention any thing about EL - probably because
it only requires jsp 1.2.
I would be all for a contribution to provide el support, however, I
would not want to make any enahancements a requirement - in order to
keep compatible with the minimium spec versions required.
David
Yujin Kim wrote:
> Hello,
>
> Just wondering if there is a reason why pluto doesn't support EL in
> portlet:param tag.
> I am also curious to know how other containers/portals handle it as well.
> If there's no specific reason, we would be happy to add that in.
>
> Thanks
>
Re: EL support in PortletParam
Posted by "David H. DeWolf" <dd...@apache.org>.
Got it, thanks. It'll probably be a week or so (after the 1.0.1
release) before I get to it. . .
David
Yujin Kim wrote:
> In case you haven't seen it,
> http://issues.apache.org/jira/browse/PLUTO-165
>
> On 9/1/05, David H. DeWolf <dd...@apache.org> wrote:
>
>>Sounds great to me.
>>
>>Yujin Kim wrote:
>>
>>>Thanks David for your asnwer.
>>>
>>>I was thinking along the line of how struts provided struts-el taglib
>>>separately since
>>>the one that's currently included should have EL support for JSP 2.0
>>>engines anyway.
>>>I was hoping it would be part of the pluto contrib package or
>>>something along the line, so the EL supported taglib can be just an
>>>extension of the main taglib but EL supported taglib is not invasive
>>>to the main taglib. Will that work?
>>>
>>>
>>>On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
>>>
>>>
>>>>The specification does not mention any thing about EL - probably because
>>>>it only requires jsp 1.2.
>>>>
>>>>I would be all for a contribution to provide el support, however, I
>>>>would not want to make any enahancements a requirement - in order to
>>>>keep compatible with the minimium spec versions required.
>>>>
>>>>David
>>>>
>>>>Yujin Kim wrote:
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>Just wondering if there is a reason why pluto doesn't support EL in
>>>>>portlet:param tag.
>>>>>I am also curious to know how other containers/portals handle it as well.
>>>>>If there's no specific reason, we would be happy to add that in.
>>>>>
>>>>>Thanks
>>>>>
>>>>
>>>>
>>
>
Re: EL support in PortletParam
Posted by Yujin Kim <ne...@gmail.com>.
In case you haven't seen it,
http://issues.apache.org/jira/browse/PLUTO-165
On 9/1/05, David H. DeWolf <dd...@apache.org> wrote:
> Sounds great to me.
>
> Yujin Kim wrote:
> > Thanks David for your asnwer.
> >
> > I was thinking along the line of how struts provided struts-el taglib
> > separately since
> > the one that's currently included should have EL support for JSP 2.0
> > engines anyway.
> > I was hoping it would be part of the pluto contrib package or
> > something along the line, so the EL supported taglib can be just an
> > extension of the main taglib but EL supported taglib is not invasive
> > to the main taglib. Will that work?
> >
> >
> > On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
> >
> >>The specification does not mention any thing about EL - probably because
> >>it only requires jsp 1.2.
> >>
> >>I would be all for a contribution to provide el support, however, I
> >>would not want to make any enahancements a requirement - in order to
> >>keep compatible with the minimium spec versions required.
> >>
> >>David
> >>
> >>Yujin Kim wrote:
> >>
> >>>Hello,
> >>>
> >>>Just wondering if there is a reason why pluto doesn't support EL in
> >>>portlet:param tag.
> >>>I am also curious to know how other containers/portals handle it as well.
> >>>If there's no specific reason, we would be happy to add that in.
> >>>
> >>>Thanks
> >>>
> >>
> >>
> >
>
>
Re: EL support in PortletParam
Posted by "David H. DeWolf" <dd...@apache.org>.
Sounds great to me.
Yujin Kim wrote:
> Thanks David for your asnwer.
>
> I was thinking along the line of how struts provided struts-el taglib
> separately since
> the one that's currently included should have EL support for JSP 2.0
> engines anyway.
> I was hoping it would be part of the pluto contrib package or
> something along the line, so the EL supported taglib can be just an
> extension of the main taglib but EL supported taglib is not invasive
> to the main taglib. Will that work?
>
>
> On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
>
>>The specification does not mention any thing about EL - probably because
>>it only requires jsp 1.2.
>>
>>I would be all for a contribution to provide el support, however, I
>>would not want to make any enahancements a requirement - in order to
>>keep compatible with the minimium spec versions required.
>>
>>David
>>
>>Yujin Kim wrote:
>>
>>>Hello,
>>>
>>>Just wondering if there is a reason why pluto doesn't support EL in
>>>portlet:param tag.
>>>I am also curious to know how other containers/portals handle it as well.
>>>If there's no specific reason, we would be happy to add that in.
>>>
>>>Thanks
>>>
>>
>>
>
Re: EL support in PortletParam
Posted by Yujin Kim <ne...@gmail.com>.
Thanks David for your asnwer.
I was thinking along the line of how struts provided struts-el taglib
separately since
the one that's currently included should have EL support for JSP 2.0
engines anyway.
I was hoping it would be part of the pluto contrib package or
something along the line, so the EL supported taglib can be just an
extension of the main taglib but EL supported taglib is not invasive
to the main taglib. Will that work?
On 8/31/05, David H. DeWolf <dd...@apache.org> wrote:
> The specification does not mention any thing about EL - probably because
> it only requires jsp 1.2.
>
> I would be all for a contribution to provide el support, however, I
> would not want to make any enahancements a requirement - in order to
> keep compatible with the minimium spec versions required.
>
> David
>
> Yujin Kim wrote:
> > Hello,
> >
> > Just wondering if there is a reason why pluto doesn't support EL in
> > portlet:param tag.
> > I am also curious to know how other containers/portals handle it as well.
> > If there's no specific reason, we would be happy to add that in.
> >
> > Thanks
> >
>
>