Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: pass (nike.apache.org: domain of andrew.rw.robinson@gmail.com
 designates 209.85.160.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=UvL7D6L3LNRCEDfge0Z0/09C0KgBkiuBX/uoGEK8ri86IQwTqSi6ajHG+d/IY8gHxo
         XlTwlxORCwuCGMWF9r+DP8qdo3QwgTkZ6hrASPmygwmeVgKrEenI5K+tf2FUalomMjbn
         V5W6kkX0ffKTDIZnBKUY9mxP0kdDuDMSt4cjM=
MIME-Version: 1.0
In-Reply-To: <n2x71235db41004090752h1b5d6a1qfdcb82919542d065@mail.gmail.com>
References: <i2jbc36a6211004051651kdb831e11nefac40b7690df138@mail.gmail.com>
	 <4BBC97BD.10507@oracle.com>
	 <g2z71235db41004090548i7f098e0eqf8dad1471845dfd3@mail.gmail.com>
	 <4BBF3675.4000904@oracle.com>
	 <m2g71235db41004090733n12e9b604v644a1b361686c618@mail.gmail.com>
	 <n2x71235db41004090752h1b5d6a1qfdcb82919542d065@mail.gmail.com>
Date: Mon, 19 Apr 2010 11:37:01 -0600
Message-ID: <l2ubc36a6211004191037q55a48fe2o2173f42666ec52b7@mail.gmail.com>
Subject: Re: [Trinidad 2] AJAX branch ready for testing
From: Andrew Robinson <andrew.rw.robinson@gmail.com>
To: MyFaces Development <dev@myfaces.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

_ajaxOldDomElements is code in Page.js, this looks like a bug in
Trinidad that needs to be fixed


On Fri, Apr 9, 2010 at 8:52 AM, Matthias Wessendorf <matzew@apache.org> wro=
te:
> looks like the 2.0.1 are just labeled as "Mojarra 2.0.2 (SNAPSHOT 2009120=
4)"
>
> I now updated the pom to "2.0.2" and got this log:
> "INFO: Initializing Mojarra 2.0.2 (FCS b10) "
>
> But the error is the same on the "clientBehaviorHolder.xhtml" page
>
> -Matthias
>
> On Fri, Apr 9, 2010 at 4:33 PM, Matthias Wessendorf <matzew@apache.org> w=
rote:
>> eh, funny.
>>
>> the pom is actually configured with "2.0.1".
>>
>> Something is going wrong here :-)
>>
>> On Fri, Apr 9, 2010 at 4:15 PM, Max Starets <max.starets@oracle.com> wro=
te:
>>> Matthias,
>>>
>>> Are you getting the same results with Mojarra 2.0.1?
>>>
>>> Max
>>>
>>> Matthias Wessendorf wrote:
>>>
>>> hi,
>>>
>>> I gave it a quick try. Here are my results:
>>>
>>> Page:
>>> http://localhost:8080/trinidad-demo/faces/demos/clientBehaviorHolder.xh=
tml
>>>
>>> JSF_RI (Mojarra 2.0.2 (SNAPSHOT 20091204)) results:
>>>
>>> I entered some text and clicked "submit via JSF Ajax"
>>>
>>> Got this (in an alert JS box):
>>> httpError: The Http Transport returned a 0 status code. =A0This is
>>> usually the result of mixing ajax and full requests. =A0This is usually
>>> undesired, for both performance and data integrity reasons.
>>>
>>> second click on the same button I got this JS error.
>>>
>>> mojarra is not defined
>>> [Break on this error] var func =3D new Function("event", handler);
>>>
>>> =3D=3D=3D> the "submit" button works.
>>>
>>> MyFaces 2.0.0-SNAPHOT results:
>>> (using snapshot since the ViewExpiredException is gone in latest snapsh=
ot )
>>>
>>> * "submit" button gives me this ALERT() box:
>>> "TypeError: this._ajaxOldDomElements is null"
>>>
>>> followed by this:
>>> "malformedXML--"
>>>
>>> * Submit via JSF Ajax:
>>>
>>> I get this alert() BOX:
>>> "httpError-httpError-Request failed"
>>>
>>>
>>> Are there any other pages where I can test the new functionality ?
>>>
>>> -Matthias
>>>
>>>
>>> On Wed, Apr 7, 2010 at 4:33 PM, Max Starets <max.starets@oracle.com> wr=
ote:
>>>
>>>
>>> Just a few minor additions -
>>> - PartialViewContext.isAjaxRequest() will be returning true for the req=
uests
>>> sent with jsf ajax
>>> as well as the legacy "partialSubmit=3Dtrue" requests.
>>> - Trinidad's partial triggers will be honored for the jsf ajax requests=
.
>>> However, this will currently work only with execute=3D"@all". Once we s=
tart
>>> adding trigger listeners
>>> during the PostRestoreView event processing, instead of decode, this
>>> limitation will go away.
>>>
>>> Max
>>>
>>>
>>> Andrew Robinson wrote:
>>>
>>>
>>> Well after a bit of work, the JSF2 AJAX branch is ready for testing to
>>> see if we want to merge it into the trunk.
>>>
>>> Branch:
>>> https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3
>>>
>>> Details:
>>> - jsf.ajax.request used to submit PPR requests from the request queue
>>> - server serves JSF2 payload, differing if an IFRAME submission is
>>> detected for Trinidad to send down script libraries
>>> - iframe processing through legacy code, but updated to use a valid JSF=
2
>>> payload
>>> - iframe still sends Tr-XHR-Message to let the server know its a legacy
>>> request
>>> - legacy request supports DOM replacement but none of the new
>>> functionality of JSF2 (attribute updates for example)
>>> - TrPage integrated with JSF2 events to correctly broadcast DOM change
>>> notifications and restore focus
>>> - If users find errors in the jsf.js libraries, setting the
>>> _useJsfBuiltInAjaxForXhr property of the request queue to false will
>>> bypass usage of jsf.ajax. We can add support for a public way of doing
>>> this later if necessary.
>>> - Server side integration with the JSF2 APIs and client behaviors,
>>> JSF2 submission working along side of partialSubmit=3Dtrue and auto PPR=
.
>>>
>>> Thank you,
>>> Andrew
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>