Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <33573.10.0.0.5.1108160237.squirrel@www.agssa.net>
In-Reply-To: <420B66EB.8040607@apache.org>
References: <40CD7782.1070009@apache.org> <420A26B6.3020809@apache.org>
    <420A4ABA.4080601@apache.org> <420A511A.1030501@apache.org>
    <34258.10.0.0.5.1107972825.squirrel@www.agssa.net>
    <420A6B65.6090106@apache.org>
    <34472.10.0.0.5.1107981773.squirrel@www.agssa.net>
    <420A8BB4.7000100@apache.org> <cufahv$c7n$1@sea.gmane.org>
    <420B66EB.8040607@apache.org>
Date: Fri, 11 Feb 2005 16:17:17 -0600 (CST)
Subject: Re: FOM inconsistency (was Re: [VOTE] Unrestricting the FOM)
From: "Antonio Gallardo" <agallardo@agssa.net>
To: dev@cocoon.apache.org
User-Agent: SquirrelMail/1.4.3a-6.FC2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal

On Jue, 10 de Febrero de 2005, 7:51, Sylvain Wallez dijo:
> oceatoon wrote:
>
>>>>Hmm... the problems is that "cocoon.request.blah" was released and
>>>> maybe
>>>>is used is used (by us and other people?) in a lot of places and maybe
>>>>other peopl! :-(
>>>>
>>>>
>>Sorry for peecking into this post but till today I thought
>>cocoon.request.blah was a normal call, and seemed quite natural ;) in a
>>users perspective. I do use it massively.
>>
>>So the correct way of doing this would be
>>cocoon.request.getParameter("blah") then ?
>>
>>
>
> Exactly. Don't know yet how/if parameters will be available as
> properties in the future, but for sure cocoon.request.getParameter()
> will always work.
>
>>before it blows off with 2.2
>>
>>
>
> Poof :-)

What a big poof! It reached 2.1.7-dev!!! ;-)

I found time to update the SVN version and an application that works fine
using the lastest SVN version seems to be broken.

I added 2 lines in javascript flow code for test:

cocoon.log.error("name=" + cocoon.request.name);
cocoon.log.error("name=" + cocoon.request.getParameter("name"));

And the result is:

name=undefined
name=antonio


Then the original "cocoon.request.name" is not working anymore. It was
simply a very big poof! ;-)

Seriously, can you review the change just to deprecate it. :-)

Best Regards,

Antonio Gallardo


>
> Sylvain
>
> --
> Sylvain Wallez                                  Anyware Technologies
> http://www.apache.org/~sylvain           http://www.anyware-tech.com
> { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
>