MyFaces Ajax Architecture
I started to work with Java in 1999 and concentrated on J2EE in the past three years. I have made my school project on the topic “Java, XML and web services” last year and wrote my diploma work “WML RenderKit for JavaServer Faces” this spring. WML is a markup language adapted to requests of small devices (mobile phones, PDAs...). I have created one of the first RenderKits for JSF and the really first for WML. After completion I have contributed this RenderKit to the MyFaces project.
I’m a student in the 5th grade at the Brno University of Technology, Faculty of Information Technology. Final exams are on 20th of June, wish me luck :-). I would like to continue my studies at the Faculty of Business and Management to extend my economical knowledge and practice my English.
JavaServer Faces is a standardized server-side user interface framework for J2EE applications and uses the MVC design pattern. JSF is using a system of components that are separating the developer from the generated code. Components generate and process requests from the client’s device. Thanks to this is possible to generate output exactly adapted to the client (web browser, mobile phone, telnet terminal...)
What is Ajax and how it works?
Why JSF and Ajax?
Ajax can be used in a wide range in connection with JSF. I will try to enumerate same examples:
- real-time server side validation
- automatical update of changes of models at the client
- really interactive components like tree controls, menus, progress bars
- and much more...
As you can see, there is a need of an API that will provide Ajax component creation functionality. This would ensure receivment of requests and calling the right method of the controller to process Ajax request. I would like to create a complete strategy of creating Ajax components in MyFaces framework and implement a server side API. All this parts must be flexible enough to support several sort of Ajax components.
The last part would be an implementation of at least one of Ajax component. It will demonstrate how to use API to create Ajax components.
Shedule and Milestones
- 14 June: Proposal deadline
- 24 June: Acceptance or rejection of proposal
- 25 June – 10 July: detailed analysis, consultation and preparing implementation
- 11 July – 10 August: API implementation, testing and documentation
- 11 August – 20 August: implementation of the samples Ajax components
- 21 August – 30 August: final form