Best Practices for JSF Portlet Migration and Development

Transcription

1 Best Practices for JSF Portlet Migration and Development IBM WebSphere Portal: Open Mic April 23, 2013 Jaspreet Singh Architect for RAD Portal tools Mansi Gaba Staff software engineer for RAD Portal tools IBM Industry Cloud Solutions Powered by IBM SmartCloud Meetings

2 Speakers Jaspreet Singh is the Architect for RAD Portal tools in the IBM Industry Cloud Solutions team based out of Delhi NCR. His area of expertise includes Java EE technology, both server side and client side, Eclipse, Portal domain, SOA etc. He is a regular speaker at international IBM conferences and has presented at RSDC 2008 (Orlando), PEC 2009 (San Diego), Innovate 2010 (Orlando), XwX Conference 2011 (Orlando), XwX Conference 2012 (Berlin), XwX Conference 2013 (Berlin) and IBM Connect 2014 (Orlando). He has also authored an essay in International Journals of Web Portals in Apart from that he has multiple patents and has written multiple articles on my technical expertise domain on IBM developerworks site. Mansi Gaba is a Staff software engineer for RAD Portal tools in the IBM Industry Cloud Solutions team based out of Delhi NCR. Her areas of expertise include WebSphere Portal, JavaServer Faces (JSF) portlet bridge, JSF technology on WebSphere Portal, JSR 286 portlet, portlet server tooling domain, Eclipse, and user interface technologies and frameworks. She has completed Sun Certified Java Programmer, Sun Certified Web Component Developer, and Oracle Certified Professional, Java EE 5 Business Component Developer. She has authored many articles related to RAD portal tooling and JSF portlets on IBM developerworks. 2

3 Please Note IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here. 3

4 Agenda Development ojsf on Portal Migration and Best Practices ojsf 2.0 Configuration Third Party UI Libraries ojsf 2.0 third party UI libraries What Next? ocontext Dependency Injection (CDI) ojsf 2.2 4

5 Agenda Development ojsf on Portal Migration and Best Practices ojsf 2.0 Configuration Third Party UI Libraries ojsf 2.0 third party UI libraries What Next? ocontext Dependency Injection (CDI) ojsf 2.2 5

6 JSF Why a special case on Portal? 6

7 Important Actors JavaServer Faces WebSphere Portal JSF Portlet Bridge Wrapper Classes 7

8 Mapping between Portlet Phases and JSF Phases Lifecycle execute() Action Request Faces Portlet processaction() Faces Portlet render() Call Call Lifecycle execute() Render Request Restore View Restore View Apply Request Values Apply Request Values Process Validations Process Validations Update Model Values Update Model Values Invoke Application Invoke Application Render Response Lifecycle render() Faces Portlet render() Call Render Response Lifecycle render() 8

9 Demo: JSF 2.0 Portlet Sample using standard faces UI Components 9

10 Agenda Development ojsf on Portal Migration and Best Practices ojsf 2.0 Configuration Third Party UI Libraries ojsf 2.0 third party UI libraries What Next? ocontext Dependency Injection (CDI) ojsf

11 Migration Scenario Deploy JSF 1.x portlet application on JSF 2.0 runtime using JSF 1.2 bridge Deploy JSF 1.x portlet application on JSF 2.0 runtime using JSF 2.0 bridge Deploy JSF 1.x portlet application on JSF 2.0 runtime using JSF 2.0 bridge (Changing view from JSP to Facelet) 11

12 Configuration Files for a JSF 2.0 portlet project Faces-Config.xml Faces-config.xml is present in WebContent\WEB-INF folder It is a configuration file which contains the information about the view components and the navigation flows in the application Portlet.xml Portlet.xml is present in WebContent\WEB-INF folder The portlet.xml descriptor is the standard portlet descriptor file which contains information about the portlet configuration 12

13 Face-Config.xml 13

14 Portlet.xml 14

15 Best Practices Development o o o o o o Portlet render parameter Use of Multiple Action Execution Request scope managed beans PortletRequestAttributeListener Implict navigation KeyManager Migration 15

16 Enable tracing for JSF 2.0 portlet bridge Tracing can be enable using the string com.ibm.faces20.portlet.*=all Trace file is generated at < WP-profile >\logs\websphere_portal JSF20 portlet bridge binary is located at <WAS-HOME>\ plugins\com.ibm.ws.prereq.jsfportlet.jar The trace file would contain JSF 2.0 portlet bridge log statements e.g [7/26/12 15:18:08:096 IST] FaceletPortlet com.ibm.faces20.portlet.faceletportletviewhandler restoreview viewid /TestPortletView.xhtml 16

17 Logging and Tracing 17

18 DEMO: Migration of JSF 1.2 portlet application to JSF 2.0 portlet application 18

19 Agenda Development ojsf on Portal Migration and best practices ojsf 2.0 Configuration Third-Party UI Libraries ojsf 2.0 third party UI libraries What Next? ocontext Dependency Injection (CDI) ojsf

20 JSF 2.0 Third-party libraries PrimeFaces RichFaces Trinidad IceFaces Samples available at: Troubleshooting Enable tracing and analyze the caused by stack trace Refer forums of JSF third party components to find if its known issue or incorrect usage of third party UI artifacts 20

21 Demo: JSF 2.0 Portlet Sample using Prime Faces UI Components 21

22 Agenda Development ojsf on Portal Migration and Best Practices ojsf 2.0 Configuration Third Party UI Libraries ojsf 2.0 third party UI libraries What Next? ocontext Dependency Injection (CDI) ojsf

23 Context Dependency Injection (CDI) Using CDI @Decorators IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. 23

24 JSF 2.2 and JSR 362 specs New features of JSF 2.2 o Performance : Stateless views o Markup evolution : HTML5 friendly markup o Flows and resource library contracts :Multi-tenancy and modularity JSR 362 Specs IBM s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion. 24

25 Thank you 25

26 Press *1 on your telephone to ask a question. Visit our Support Technical Exchange page or our Facebook page for details on future events. To help shape the future of IBM software, take this quality survey and share your opinion of IBM software used within your organization: IBM Collaboration Solutions Support page IBM Collaboration Solutions Support 26