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 Affects Versions: 2.0.0-beta Environment: Windows Mobile 6.1 Reporter: Mamallan Uthaman
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.6 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, and interestingly, <f:ajax> does seem to work in BB 4.6. 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, BB 4.6 crashed when I tested <f:ajax> with Trinidad components. I suspect the reason is, though <f:ajax> does work with MyFaces components, MyFaces's Ajax mechanism is probably not robust enough to handle Trinidad components in BB 4.6. To be specific,I believe the crashed happened while executing jsf.ajax.response. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.