I can see this page failing with JS errors in chrome. I'll have a look
On Tue, Apr 20, 2010 at 7:59 AM, Matthias Wessendorf <mat...@apache.org> wrote: > on the pprDemos.jspx stuff, there is a bunch of "tests" for PPR, > > one of the has the header "Command components with partialSubmit", which > does not work (in the trinidad demo) > > File (in SVN) is located there: > > https://svn.apache.org/repos/asf/myfaces/trinidad/branches/jsf2_ajax.3/trinidad-examples/trinidad-demo/src/main/webapp/demos/pprDemos.jspx > > On Tue, Apr 20, 2010 at 6:37 AM, Max Starets <max.star...@oracle.com> wrote: >> Matthias, >> >> What do you mean when you say 'command components with partialSubmit do not >> work'? >> >> Thanks, >> Max >> >> On Apr 20, 2010, at 3:26 AM, Matthias Wessendorf <mat...@apache.org> wrote: >> >>> Checked Mojarra 2.0.1 and MyFaces 2.0.0 (out soon) >>> >>> - both have the NPE filed in TRINIDAD-1786 >>> >>> * Mojarra: >>> -PPR on select* works (exception see above) >>> - "Command components with partialSubmit" does _not_ work >>> >>> * MyFaces: >>> - all PPR stuff does a full page-refresh >>> >>> I am fine in merging these bits to trunk, but before we acutally >>> do a release, we should check what's going wrong in MyFaces/Trinidad ;-) >>> (I think it must be an issue in MyFaces, so once I have some more time, >>> I will file a bug against that, with a little better description) >>> >>> -Matthias >>> >>> On Tue, Apr 20, 2010 at 9:09 AM, Matthias Wessendorf <mat...@apache.org> >>> wrote: >>>> >>>> Ok, looks like you are talking about JSF2's JS/Ajax stuff. >>>> >>>> The term mojarra is slightly confusing, since I understand it >>>> as a specific dependency to that particular implementation. >>>> >>>> But looks like we do not have that, for the ajax stuff, which is >>>> great. >>>> >>>> -Matthias >>>> >>>> On Tue, Apr 20, 2010 at 9:05 AM, Matthias Wessendorf <mat...@apache.org> >>>> wrote: >>>>> >>>>> On Mon, Apr 19, 2010 at 11:58 PM, Andrew Robinson >>>>> <andrew.rw.robin...@gmail.com> wrote: >>>>>> >>>>>> The branch is ready and the issues that were brought up in this thread >>>>>> as well as other issues have been resolved. Unless there are any >>>>>> objections, I will merge the changes into the trunk tomorrow. >>>>> >>>>> fine here. >>>>> >>>>>> >>>>>> Note that Max added a switch to be able to turn off PPR through JSF at >>>>>> the agent level so that mobile browsers that fail with the mojarra >>>>>> JavaScript can go back to the legacy code. >>>>> >>>>> not sure I understand: why is that switch mojarra specific ? >>>>> Or are you just saying that it's a fallback to JSF2 ? >>>>> >>>>> -Matthias >>>>> >>>>>> >>>>>> -Andrew >>>>>> >>>>>> >>>>>> On Wed, Apr 7, 2010 at 8:33 AM, 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 >>>> >>> >>> >>> >>> -- >>> 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 >
