Mobile JSF vs MyMobileWeb

We have been evaluating Mobile JSF an open source product intended to the development of mobile web applications, which has been recently released by Ericsson. The main conclusion is that it is a couple of light years behind MyMobileWeb. The most important limitations of Mobile JSF with respect to MyMobileWeb are:

• Mobile JSF’s device database contains only a minimal set of devices with a minimal set of properties. This fact has led us to the conclusion that Mobile JSF is not doing any kind of advanced content adaptation. They only send the correct markup to each device, but as we know, that is not enough. Remember that MyMobileWeb uses a bunch of properties to adapt to devices, the majority of them coming from WURFL.
• CSS Media Queries selection mechanisms are not as flexible as the style overriding mechanisms provided by MyMobileWeb. For instance, in MyMobileWeb, using style overriding, one can, very easily, to set up different layouts for different devices.
• Content selection based on CSS Media Queries is not efficient nor feasible in terms of bandwidth consumption. MyMobileWeb selects content at the server side which is far more efficient
• Automatic Pagination functionalities are not present in Mobile JSF
• Automatic Validations based on script on the client side are not supported by Mobile JSF
• The set of user interface components is very poor compared to MyMobileWeb’s

Conclusion: Mobile JSF is not an alternative to MyMobileWeb.