cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <va...@reverycodes.com>
Subject Re: [RFC] JXTG Refactoring
Date Mon, 20 Dec 2004 14:02:19 GMT
Daniel Fagerstrom wrote:
> Christopher Oliver wrote:
> 
>> If you ask me, this is mainly a semantic problem, not a technical one.
>>
>> If a template is not called from a (Javascript) flowscript, there is 
>> no FOM, and therefore no FOM variables are available in JXTG. For the 
>> case where it _is_ called from a flowscript, then the FOM is and IMO 
>> should be accessible.
>>
>> The request, session, etc, variables that are described as deprecated 
>> are unnecessary and inappropriate when the template is called from the 
>> flowscript (since they provide no additional information beyond the 
>> FOM, but yet have an "impedance mismatch" with the flowscript model). 
>> They are simply carried over from the original (pre-FOM) 
>> implementation for backward compatibility.
> 
> 
> Thanks for clarifying. IMO we should just remove the pre-FOM stuff from 
> the refactored JXTG, we cannot support deprecated things for ever.

I'm -1 on this as long as there is no "FOM" in JXTG outside of flow environment. 
After "FOM" is present in the JXTG, "non-FOM" request/response/etc variables 
should go through regular deprecation cycle (i.e., 1/2 year or so) according to 
Cocoon's versioning guide.

Vadim

Mime
View raw message