commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <ge...@adeptra.com>
Subject Re: Proposal: JSP/JSTL expression language
Date Sat, 20 Jul 2002 17:02:52 GMT
On 7/20/02 6:11 AM, "Stephen Colebourne" <scolebourne@btopenworld.com>
wrote:

> I knew I had a sense of deja vu. So the question becomes, can the JSP EL and
> JEXL projects become simply plugins to, or part of the JEX project?

I don't think that's the right way to go - I think that JEX should (if it
wants to) support all of these things.  But my feeling is that any kind of
scriptish project should be independent (for purposes of innovation...)


> 
> Stephen
> 
>> 100% agree with you. There are a lot of "good" scripts, languages and
> QL's,
>> it is not a problem to invent a new one, but it is better to allows users
> to
>> write or
>> use some "the best" language.
>> 
>> We can import code to sandbox without vote, but it is my
>> -0 for a new "el for JSP" in commons, I don't think it is something common
>> for Jakarta
>> projects and it is possible to find a better place for "el".
>> 
>> 
>> BTW:
>> commons-sandbox/jex is an interface for plugged in syntaxes for
> evaluation.
>> 
>>> +1 on joining commons, but...
>>> 
>>> My query is over how general the interface could be. I haven't looked at
>> it
>>> in much detail, but it seems like there are multiple possible 'element
>>> language' syntaxes - JSP and JEXL are only two. What about xpath for
>>> example? Is the plan to create an interface that allows users to write
>> their
>>> own plugged in syntaxes? If so, maybe 'path' is a more general name than
>>> 'el'.
>>> 
>>> eg.
>>> Path.evaluate("fred.bob.vera", Path.JEXL);
>>> Path.evaluate("fred/bob/vera[0]", Path.XPATH);
>>> 
>>> Stephen
>>> 
>>> ----- Original Message -----
>>> From: <costinm@covalent.net>
>>> To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
>>> Sent: Friday, July 19, 2002 9:57 PM
>>> Subject: Re: Proposal: JSP/JSTL expression language
>>> 
>>> 
>>>> +1 on both JSP/JSTL EL and JEXL - as part of commons.
>>>> 
>>>> I also like to be sure that:
>>>> 
>>>> 1) jasper will allow customization on what EL impl it uses.
>>>> 2) the EL implementations can be used easily in other projects.
>>>> 
>>>> Costin
>>>> 
>>>> On Thu, 18 Jul 2002, Geir Magnusson Jr. wrote:
>>>> 
>>>>> On 7/18/02 5:29 PM, "bob mcwhirter" <bob@werken.com> wrote:
>>>>> 
>>>>>>> Hi there.  I'm the reference-implementation lead for the JSP
>> Standard
>>> Tag
>>>>>>> Library (JSTL), which includes an expression language ("EL")
that
>>> will
>>>>>>> become the basis of JSP 2.0's expression language.  Because of
> the
>>> number
>>>>>>> of different projects that need the EL, many of us thought it
> wise
>> to
>>>>>>> propose that Jakarta Commons host the implementation.  This will
>> also
>>>>>>> allow the addition of nonstandard features that some people
> desire,
>>> so
>>>>>>> long as the code base has a mode of operation whereby the JSTL
> 1.0
>>> and JSP
>>>>>>> 2.0 standards (separately) obtain.
>>>>>> 
>>>>>> Is this different from Jexl, which I thought was part of the
>> reference
>>>>>> impl of the JSTL?
>>>>>> 
>>>>>>   http://jakarta.apache.org/commons/sandbox/jexl/
>>>>>> 
>>>>> 
>>>>> Jexl is *not* in any way part of the RI.
>>>>> 
>>>>> Jexl strives to be compliant with the RI, but also extends it in
> what
>>> some
>>>>> consider useful ways, such as access to arbitrary methods of objects
>> in
>>> the
>>>>> context.
>>>>> 
>>>>> I am all for JSTL becoming a Commons component if Jexl can as well.
>> If
>>> JSTL
>>>>> rules out other competing implementations, I'm -1.
>>>>> 
>>>>> I'll put together a Jexl proposal as well.  Jelly is probably going
> to
>>> come
>>>>> over the wall sometime as well, so as Jelly requires Jexl, I might
> as
>>> well
>>>>> be here and ready :)
>>>>> 
>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> --
>>>> To unsubscribe, e-mail:
>>> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
>>>> For additional commands, e-mail:
>>> <mailto:commons-dev-help@jakarta.apache.org>
>>>> 
>>> 
>>> 
>>> --
>>> To unsubscribe, e-mail:
>> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
>>> For additional commands, e-mail:
>> <mailto:commons-dev-help@jakarta.apache.org>
>>> 
>> 
>> 
>> --
>> To unsubscribe, e-mail:
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
>> For additional commands, e-mail:
> <mailto:commons-dev-help@jakarta.apache.org>
>> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 

-- 
Geir Magnusson Jr. 
Research & Development, Adeptra Inc.
geirm@adeptra.com
+1-203-247-1713



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message