1. Which technology will be used to implement this interface? SI4 Project by Pierre Arnoux, Jérémy Benabu, Steve Colombié and Xavier Gentile Supervised by Mireille Blay-Fornarino and Sébastien Mosser Friday, 12 th June, 2009 1

2. Structure Project context PHP user interface JSF user interface Comparison Conclusion 2 Project context › PHP user interface › JSF user interface › Comparison › Conclusion

3. Project context › Existent Project context › PHP user interface › JSF user interface › Comparison › Conclusion 3 Photos Events Menus INTERFACE (to do) Bad way! Data base Good way!

4. Project context › Objectives Which technology is the best? Project context › PHP user interface › JSF user interface › Comparison › Conclusion 4 STRUTS ?.NET ? PHP ? JSP/JSF ? … PHP ? JSF ?

5. Project context › Objectives Criteria to compare Diffusion & reliability Installation cost Use cost Interoperability Project context › PHP user interface › JSF user interface › Comparison › Conclusion 5

6. Project context › Planning planning Project context › PHP user interface › JSF user interface › Comparison › Conclusion 6 Use of existing Web Services  Jérémy Benabu & Steve Colombié  Pierre Arnoux & Xavier Gentile Jérémy Benabu & Steve Colombié  Pierre Arnoux & Xavier Gentile 

7. PHP user interface NUSOAP library Easy installation Well documented Lot of examples Apache PHP is executed by the server Easy PHP Project context › PHP user interface › JSF user interface › Comparison › Conclusion 7

8. Index.phpIndex.php MenusMenus DeleteDelete ModifyModify CreateCreate ListingListing CoursesCourses CreateCreateDeleteDelete ModifyModifyListingListing Proxy Proxy Courses_proxiesCourses_proxiesMenus_proxiesMenus_proxies ProxyProxy NuSOAP NuSOAP nusoapnusoap Class Class. nusoapmimenusoapmime PHP user interface › Architecture Project context › PHP user interface › JSF user interface › Comparison › Conclusion 8

9. PHP user interface › Development Class Proxy (client): Call web service with WSDL Call methods Classes Courses / Menus Use their own proxy Object One file for each functionnality Easy to call a method (by generic function) Complex to receive parameters Project context › PHP user interface › JSF user interface › Comparison › Conclusion 9 Proxy Server WSDL Request SOAPClient Answer

10. PHP user interface › Demonstration Project context › PHP user interface › JSF user interface › Comparison › Conclusion 10

11. JSF user interface › Architecture Project context › PHP user interface › JSF user interface › Comparison › Conclusion 11 JSF Pages Managed Bean WebServices Java-based Web Application framework JSF uses a component-based approach

12. JSF user interface › Development Managed Bean : Getting WSDL’s Webservice Creating methods Calling the WebService methods intuitively Called by JSF pages easily Project context › PHP user interface › JSF user interface › Comparison › Conclusion 12 Managed Bean Controller Managed Bean Controller Web Service WSDL

13. JSF user interface › Demonstration Project context › PHP user interface › JSF user interface › Comparison › Conclusion 13

14. Comparison Project context › PHP user interface › JSF user interface › Comparison › Conclusion 14 JAVA API VersusVersus JSF PHP

15. Comparison Project context › PHP user interface › JSF user interface › Comparison › Conclusion 15 Massively used Few and not really well detailed

16. Comparison Project context › PHP user interface › JSF user interface › Comparison › Conclusion 16 Installation of an Apache Server Not Assured (NU SOAP) Every server (Apache, Glassfish…) Seems to be assured (standard)

17. Comparison Project context › PHP user interface › JSF user interface › Comparison › Conclusion 17 Volume per service By the controller 3 modules : Proxy Interface (heavy) Methods to manage types (very heavy) By the controller 2 short files : Interface JSF (easy) Controller Java

18. Comparison Project context › PHP user interface › JSF user interface › Comparison › Conclusion 18 Types Management Very Easy Not so simple ! It Needs some learning !

19. Comparison › Results JSF is reliable (it’s a standard made by Sun) JSF is lighter than PHP to build interfaces. JSF is easier and lighter to use than PHP for managing types (int, String…). JSF isn’t trivial to use, learning is needed.  We have chosen JSF Project context › PHP user interface › JSF user interface › Comparison › Conclusion 19

20. Conclusion JSF will be used to implement the user interfaces of the project jSeduite. In our report we had made a tutorial about JSF and how to use it. It was interesting to compare two great technologies. Project context › PHP user interface › JSF user interface › Comparison › Conclusion 20

21. Thank you for you attention Any question ? Project context › PHP user interface › JSF user interface › Comparison › Conclusion 21