[
https://issues.apache.org/jira/browse/MYFACES-2876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898401#action_12898401
]
Werner Punz edited comment on MYFACES-2876 at 8/13/10 4:17 PM:
---------------------------------------------------------------
I will start to help on the Blackberry support next week since Blackberry has
the tools available for free on the net (In fact it was on my agenda already
for 2.0.2 but I had to postpone it to fix the node leaks in ie6), I cannot help
for now with the WinMobile support until Microsoft has granted me access to
MSDN again, which is still pending and has been since january.
But as I said if someone wants to do it I am willing to help here.
As for WinMobile, I assume it all comes down to a missing browser vendor
detection on the response or dom handling side.
(mobile browsers have not been on my agenda until recently, I wanted to fortify
the code for all desktop browsers first, where we are now more solid than
Mojarra is)
The full page submit you get sounds like some severe error issued somewhere.
was (Author: werpu):
I will start to work on the Blackberry support next week since Blackberry
has the tools available for free on the net (In fact it was on my agenda
already for 2.0.2 but I had to postpone it to fix the node leaks in ie6), I
cannot help for now with the WinMobile support until Microsoft has granted me
access to MSDN again, which is still pending and has been since january.
But as I said if someone wants to do it I am willing to help here.
As for Blackberry, I assume it all comes down to a missing browser vendor
detection on the response or dom handling side.
(mobile browsers have not been on my agenda until recently, I wanted to fortify
the code for all desktop browsers first, where we are now more solid than
Mojarra is)
but I have to investigate further into it next week for Blackberry, my goal is
to get the support for the device into 2.0.2 if time permits.
The good news regarding Blackberry btw. is that the 4.6 browser is end of the
line, the new Blackberry OS already will have a webkit based browser, and there
MyFaces already works, even on the mobile editions.
> 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, Blackberry 4.7
> 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.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.
