Requirements

• Have taken a two-day course (15 hours)
• Pass a written examination on the course contents containing 10 short questions

Regulations

• Students will have to develop a mobile accessible website/application that they will install at an Internet accessible address.
• If so required, the source code of the certification application shall be made available to the instructor for inspection.
• At the end of the course and after passing the examination, students shall have 60 calendar days to develop the application.

Functionalities to be developed to attain certification

An original (copies are not acceptable) fully operational, mobile accessible website, including at least the following functions:

• A login page with a logo enabling user authentication

  

• A home menu with access to different functions, including at least:
  • The menu will have accelerator keys for each option.
  • The menu will have a grid layout for the OpenWave emulator/browser.
  • The menu shall have a vertical layout for other devices.

    

• A data search form that includes compulsory/optional select, entryfield, datefield controls, etc., with different accept types.
  • The form-driven search results will be presented as an automatically paginated table and presented using alternate colours. The table will be displayed as a single column in the case of the OpenWave emulator. The table will be displayed as two columns in the case of other devices/emulators.
  • The details of the results will be displayed in another presentation with disabled fields or read-only fields formatted in different styles and colours.

    

• A functionality requiring the use of the chainedmenu control

  

Additionally:

• The site should be displayed in at least two languages

  

• All screens should include a navigation bar with “Back” and “Home” links

  

• The user interface should be appropriately decorated with small images and have an attractive look and feel.
• Students should check for correct visualization of the certification application by the OpenWave version 7 emulators [1] and .mobi emulators [2].

Any questions about the certification exercise should be sent to mailto:mymobileweb-support@lists.morfeo-project.org

MyMobileWeb runtime execution architecture is illustrated in the figure below. At the device side, when a user interaction causes an event to be treated at the server side, it is sent an HTTP request which contains:

• the identifier of the visual control that raised the event.
• the event identifier.
• data that might have been entered by the user.

At the server side, the request is initially processed by a Controller component, which recognizes the device (if it has not been done previously). Then, data is validated, and if validations are ok, data items are stored in the context. The context is a container that holds all the model data items, and it is structured hierarchically in different scopes (application, session, use case, view, etc.).

There are two kind of events sent from the device:

• Application-specific events. These events have to do with the functionality of the application and are treated by specific handlers (methods of well-known Java classes) provided by programmers.
• MyMobileWeb-specific events. These events are common to all applications and are related to the functionalities provided by MyMobileWeb. These events are handled automatically by MyMobileWeb, so application developers need not to worry about them. For example, a next page event is raised when the user is paginating over the contents of a table.

Application-specific event handlers decide on how to process an incoming request. Typically they will call application operations (OAs) to get more data to be put into the model and, finally, a redirection to the next view (identified by a logical name) will be made. At this point, MyMobileWeb will be responsible of locating the appropriate JSP page according to the delivery context. This JSP page will render the presentation and will resolve all the data and content bindings with the help of runtime libraries. The runtume will also resolve common issues such as pagination of contents, selection of the best images, calling the image transcoding, dealing with i18N and so on.

All event-handling related operations are accessible through an API provided by the MVC framework.

The Eclipse plugin increases MyMobileWeb development productivity. It can be used to create and configure projects and create project elements (OPs, presentations, CSS) and manage the code generation process.

Download the plugin from:

http://forge.morfeo-project.org/frs/download.php/184/MyMobileWeb_EclipsePlugin_0_9.tar.gz

A user’s manual is available at:

http://forge.morfeo-project.org/wiki/index.php/Manual_de_usuario_del_Plugin_MyMobileWeb

Telefónica I+D has freed the ‘MyMobileWeb’ Mobility Channel within the MORFEO Open Software Community. This technology enables the rapid development of applications and services (both on-line and off-line) accessible from multiple mobile devices (PDAS, mobile telephones, smartphones, etc.).

The product has been developed entirely in Spain using standard open technologies (Java, XML, Servlet, JSP…). Additionally, one of the basic platform components (the Device Manager) is based on the WURFL open software component.

Telefónica I+D’s Mobility Channel is a significant innovation as compared with the state of the art of commercial multi-device access solutions. The documentation and the source code and binaries for the project can be downloaded from the website.