I too agree, lets avoid it.
On 7/28/2011 3:21 PM, Pete Muir wrote:
> I agree, I think with the proposed simplified API this is no longer a real issue.
>
> On 28 Jul 2011, at 00:50, Kin-man Chung wrote:
>
>> It was suggested before (by Chrisph Beck, I think) that ELContext be splitted into two contexts, one for EL parsing and the other for evaluation. The argument for this was in EL parsing, only the FunctionMapper and VariableMapper in the ELContext is used, and in EL evaluation, they are not used, and it would be less confusing if ELParseContext is used in createValueExpression and createMethodExpression, and ELEvaluationContext be used in ValueEpxression.getValue() etc. I thought it was a good idea, and actually included them in the proposal for JSR341.
>>
>> However, as I look into putting them in codes, I've found that it is difficult to add these two EL contexts and still be backward compatible. We'll need to deprecate most of the API and add new ones using these two. Moreover, with the new API for the stand alone EL, the user are not dealing directly with ELContext, so it is less important to have a different context for parsing and evaluation.
>>
>> Therefore, if there are no objections, I'll not include them in the JSR.
>>
>> Kin-man
>