[jira] Resolved: (MYFACES-2876) Ajax Support in Mobile Browsers

["Werner Punz (JIRA)" <de...@myfaces.apache.org>]

     [ https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Werner Punz resolved MYFACES-2876.
----------------------------------

    Fix Version/s: 2.0.2-SNAPSHOT
       Resolution: Fixed

Done I am closing this now, the f:ajax fix is still under discussion, but for now I guess we wont need it, since the browser will be hardly used for ajax anyway and who really wants to support it has to do it manually.


> Ajax Support in Mobile Browsers
> -------------------------------
>
>                 Key: MYFACES-2876
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2876
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General, JSR-314
>    Affects Versions: 2.0.0-beta
>         Environment: Windows Mobile 6.1, Blackberry 4.7
>            Reporter: Mamallan Uthaman
>             Fix For: 2.0.2-SNAPSHOT
>
>
> In Windows Mobile (WM) 6.1 platform, <f:ajax> is converted into a full-page submit instead of a PPR. The reason is unlike Webkit based mobile-browsers, WM 6.1 or Blackberry (BB) 4.7 offers only a limited JavaScript-DOM support, so we need to optimize MyFaces's Ajax mechanism to work around the limitations of mobile browsers. I used the sample code below for testing.
> Facelets code:
> <h:commandButton value="PPR">
>   <f:ajax event="action" render="second"/>
> </h:commandButton>
> <h:outputText value="#{item.date.seconds}" id="second"/>
> Item.Java:
> import java.util.Date;
> public class Item {
>   Date date;
>   public void setDate(Date date) {
>     this.date = date;
>   }
>   public Date getDate() {
>     return new Date();
>   }
> }
> faces-config:
> <managed-bean>
>   <managed-bean-name>item</managed-bean-name>
>   <managed-bean-class>Item</managed-bean-class>
>   <managed-bean-scope>request</managed-bean-scope>
> </managed-bean>
> Also, in the case of  BB 4.7 , <f:ajax> can successfully send a PPR, but PPR response is ignored. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.