I now checked this page:

http://localhost:8080/trinidad-demo/faces/demos/pprDemos.jspx

MYFACES_SNAPSHOT: =>

on any "ajax" action/click, I get these two alert() boxes:
* "TypeError: this._ajaxOldDomElements is null"
* "malformedXML--"

==> I will file a bug against MyFaces


JSF RI (2.0.2):

==> fine



On Fri, Apr 9, 2010 at 2:48 PM, Matthias Wessendorf <mat...@apache.org> wrote:
> hi,
>
> I gave it a quick try. Here are my results:
>
> Page:
> http://localhost:8080/trinidad-demo/faces/demos/clientBehaviorHolder.xhtml
>
> 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.  This is
> usually the result of mixing ajax and full requests.  This 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 = new Function("event", handler);
>
> ===> the "submit" button works.
>
> MyFaces 2.0.0-SNAPHOT results:
> (using snapshot since the ViewExpiredException is gone in latest snapshot )
>
> * "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.star...@oracle.com> wrote:
>> Just a few minor additions -
>> - PartialViewContext.isAjaxRequest() will be returning true for the requests
>> sent with jsf ajax
>> as well as the legacy "partialSubmit=true" requests.
>> - Trinidad's partial triggers will be honored for the jsf ajax requests.
>> However, this will currently work only with execute="@all". Once we start
>> 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 JSF2
>>> 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=true 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

Reply via email to