Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie JSF 2 and beyond: Keeping progress coming
Ähnlich wie JSF 2 and beyond: Keeping progress coming (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
JSF 2 and beyond: Keeping progress coming
- 1. 16-11-09 JSF 2 and beyond: Keeping progress coming Andy Schwartz - Oracle Corporation Dan Allen & Pete Muir - Red Hat, Inc.
- 2. 16-11-09 See how far JSF 2 has come, explore the community’s role and take a glimpse at JSF 2.next Goals
- 3. 16-11-09 Join in! Twitter hashtag: #jsf2next
- 4. 16-11-09 Join in! JSF 2 and beyond: BOF Tonight @ 20:00 in Room 2!
- 8. 16-11-09 Many faces of JSF 2 Andy Schwartz Dan Allen Jacob Hookom Alexandr Smirnov Ken Paulsen Martin Marinschek Matthias Wess endorf Pete Muir Alexander Jesse Imre O ßwald Yara Senger Lincoln Baxter Adam Winer Craig McClanahan Kito Mann Rick Hightower Joe Ottinger Ted Goddard Neil Griffin Jason Lee Stan Silvert David Geary Micheal Freedman Hazem Saleh Çağata Çivici Dennis Byrne Roger Keays Amy Fowler Max Katz Jeremy Grelle Keith Donald Emmanuel Bernard Ed Burns Jim Driscoll Roger Kitain Ryan Lubke Nick Belaevski Gavin King
- 10. 16-11-09 View declaration Facelets, View Declaration Language API
- 13. 16-11-09 The solution Facelets (Thanks, Jacob!)
- 15. 16-11-09 The problem revisited But, Facelets isn’t standard :(
- 16. 16-11-09 The solution revisited Now it is !
- 20. 16-11-09 Component development Java components, composite components
- 21. 16-11-09 The problem Component development is hard!
- 23. 16-11-09 The solution: Take 1 Simplify Java component development
- 25. 16-11-09 The solution: Take 2 Composite components!
- 28. Composite component definition 16-11-09 <composite:interface> <composite:attribute name = "name" default = "World" /> </composite:interface> <composite:implementation> Hello, #{cc.attrs.name}! </composite:implementation> resources/foo/greeting.xhtml
- 29. Composite component usage 16-11-09 <html xmlns = "http://www.w3.org/1999/xhtml" xmlns:h = "http://java.sun.com/jsf/html" xmlns:foo="http://java.sun.com/jsf/composite/foo" > <body> <foo:greeting name="Devoxx"/> </body> </html>
- 32. 16-11-09 Ajax jsf.ajax.request(), <f:ajax>, Ajax Java APIs, and tree visiting
- 33. 16-11-09 The problem JSF/Ajax Overload!
- 35. 16-11-09 The solution Standard Ajax APIs
- 38. jsf.ajax.request() 16-11-09 <h:outputScript name = "jsf.js" library = "javax.faces" /> ... <h:commandButton value = "Do something Ajaxy" onclick = "jsf.ajax.request(this, event, {render: ' out '}); return false;" /> ... <h:outputText id = " out " value = "Update me!" />
- 40. <f:ajax> nesting 16-11-09 <h:commandButton value = "Do something Ajaxy" > <f:ajax render = " out " /> </h:commandButton> ... <h:outputText id = " out " value = "Update me!" />
- 41. <f:ajax> wrapping 16-11-09 <f:ajax render = " out " /> <h:commandButton value = "Do something Ajaxy" /> <h:commandButton value = "Do something else" /> <h:commandButton value = "One more here" /> </f:ajax> ... <h:outputText id = " out " value = "Update me!" />
- 42. <f:ajax> client events 16-11-09 <h:commandButton> <f:ajax event = "mouseover" /> </h:commandButton> ... <h:inputText> <f:ajax event = "focus" /> </h:commandButton>
- 45. 16-11-09 Behaviors ClientBehavior, ClientBehaviorHolder
- 46. 16-11-09 The problem It’s not just about Ajax
- 48. 16-11-09 The solution New contract: separate behavior from component
- 50. ClientBehavior sample 16-11-09 @FacesBehavior ( "org.demo.behavior.Greet" ) public class GreetBehavior extends ClientBehaviorBase { @Override public String getScript(ClientBehaviorContext ctx) { return "alert('Hello, World!')" ; } }
- 51. ClientBehavior sample 16-11-09 <h:commandButton value = "Do something Ajaxy" > <f:ajax/> </h:commandButton> <h:commandButton value = "Say Hello" > <foo:greet/> </h:commandButton>
- 56. 16-11-09 State saving Partial state saving, state helper
- 57. 16-11-09 The problem State saving is nasty
- 58. 16-11-09 public Object saveState(FacesContext ctx) { if ( _values == null ) { _values = new Object[10]; } _values [0] = super .saveState(ctx); _values [1] = accesskey ; _values [2] = alt ; _values [3] = dir ; _values [4] = disabled ; _values [5] = image ; _values [6] = label ; _values [7] = lang ; _values [8] = onblur ; _values [9] = onchange ; return _values ; } public void restoreState( FacesContext ctx, Object _state) { _values = (Object[]) state; super .restoreState(ctx, _values [0]); this . accesskey = (java.lang.String) _values [1]; this . alt = (java.lang.String) _values [2]; this . dir = (java.lang.String) _values [3]; this . disabled = (java.lang.Boolean) _values [4]; this . image = (java.lang.String) _values [5]; this . label = (java.lang.String) _values [6]; this . lang = (java.lang.String) _values [7]; this . onblur = (java.lang.String) _values [8]; this . onchange = (java.lang.String) _values [9]; } State saving lunacy
- 59. 16-11-09 Another problem State saving is expensive
- 61. 16-11-09 The solution Partial state saving for smaller state. State helper utilites for happier component developers.
- 66. 16-11-09 Controller GET support, bookmarkable URLs, navigation and redirects, and resource loading
- 67. 16-11-09 GET support View metadata, view parameters, pre-render event listeners and bookmarkable URL components
- 68. Consuming 16-11-09 http://acme.org/catalog.jsf?page=2 http://acme.org/item.jsf?id=4
- 69. Initial request lifecycle 16-11-09 http://acme.org/catalog.jsf?cat=electronics&page=3&layout=grid
- 70. Initial data 16-11-09 http://acme.org/ catalog.jsf ?cat=electronics&page=3&layout=grid view ID /catalog.xhtml
- 71. Initial data 16-11-09 http://acme.org/catalog.jsf? cat=electronics&page=3&layout=grid request parameters cat=electronics page=3 layout=grid
- 72. Bean property mapping 16-11-09 <managed-bean> ... <managed-bean-property> <property-name> category </property-name> <value> #{param['cat']} </value> </managed-bean-property> </managed-bean>
- 75. Reuse the tree 16-11-09
- 76. View metadata facet 16-11-09 <f:view> <f:metadata> ... </f:metadata> ... </f:view>
- 79. View parameter 16-11-09 <f:view> <f:metadata> <f:viewParam name="cat" value="#{catalogBean.category}"/> </f:metadata> ... </f:view> UIViewParameter
- 80. View parameter w/ converter 16-11-09 <f:view> <f:metadata> <f:viewParam name = "cat" value = "#{catalogBean.category}" > <f:converter converterId="com.acme.converter.Category"/> </f:viewParam> </f:metadata> ... </f:view> UIViewParameter
- 82. View metadata templating 16-11-09 <f:view> <f:metadata> <ui:include src = "/WEB-INF/metadata/catalog.xhtml" /> [ or ] <acme:catalogMetadata/> </f:metadata> ... </f:view> More powerful & flexible than a matching pattern
- 83. 16-11-09 Post-processing The values are set, now what?
- 85. Post-mapping event listener 16-11-09 <f:view> <f:metadata> ... <f:event type = " preRenderView " listener = "#{catalogBean.onRender}" /> </f:metadata> ... </f:view> Declarative system event No-args method or method that accepts ComponentSystemEvent
- 86. Hold the rendering! 16-11-09 public void onRender() { FacesContext ctx = FacesContext.getCurrentInstance(); if (ctx.isValidationFailed() || !loadDataAttempt()) { ctx.getApplication().getNavigationHandler() .handleNavigation(ctx, null , "invalid" ); } } Force navigation if preconditions not met
- 87. Report downloads 16-11-09 <view xmlns = "http://java.sun.com/jsf/core" > <event type = "preRenderView" listener = "#{reportBean.download}" /> </view>
- 88. Pushing the file 16-11-09 public void download() { FacesContext ctx = FacesContext.getCurrentInstance(); pushFile( ctx.getExternalContext(), "/path/to/a/pdf/file.pdf" , "file.pdf" ); ctx.responseComplete() ; }
- 89. View actions 16-11-09 <f:view> <f:metadata> ... <f:viewAction execute="#{catalogBean.onRender}"/> </f:metadata> ... </f:view> Wouldn’t it be nice if we had...? JSF 2.next Including option to disable on postback
- 90. View actions 16-11-09 <navigation-rule> <from-view-id> /catalog.xhtml </from-view-id> <navigation-case> <from-action> #{catalogBean.onRender} </from-action> <from-outcome> failure </from-outcome> <to-view-id> /search.xhtml </to-view-id> </navigation-case> </navigation-rule> ...followed by buit-in navigation? JSF 2.next
- 92. How do we process this URL? 16-11-09 http://acme.org/catalog/category/electronics
- 93. Pretty URLs 16-11-09 <rewrite-rule> <rewrite-view-id> /catalog.xhtml </rewrite-view-id> <rewrite-case> <url-pattern> /catalog </url-pattern> <url-pattern> /catalog/category/ {cat} </url-pattern> <url-pattern> /catalog/category/ {cat} / {page} </url-pattern> </rewrite-case> </rewrite-rule> JSF 2.next View parameter mappings
- 97. Generating bookmarkable links 16-11-09 <h:link value = "Previous" includeViewParams = "true" > <f:param name = "page" value = "#{catalogBean.previousPage}" /> </h:link> <f:metadata> <f:viewParam name = "q" value = "#{catalogBean.query}" /> <f:viewParam name = "page" value = "#{catalogBean.page}" /> </f:metadata> http://acme.org/catalog.jsf? q=portable+hole & page=3 /catalog.xhtml
- 99. 16-11-09 Navigation Implicit, conditional and preemptive navigation, queryable navigation rules and redirect parameters
- 102. A navigation shorthand 16-11-09 <h:commandButton action = "#{productBean.save}" value = "Save" /> public String save() { // perform save logic, then... return "/catalog.xhtml" ; }
- 103. A navigation short (er) hand 16-11-09 Can link to navigation case later <h:commandButton action = "#{productBean.save}" value = "Save" /> public String save() { // perform save logic, then... return " catalog " ; } Relative to current path and view ID
- 106. A conditional case 16-11-09 <navigation-case> <from-action> #{registration.register} </from-action> <if>#{currentUser.registered}</if> <to-view-id> /account.xhtml </to-view-id> <redirect include-view-params = "true" /> </navigation-case>
- 107. Matching a void outcome 16-11-09 <navigation-case> <from-action> #{catalog.search} </from-action> <if>#{true}</if> <to-view-id> /results.xhtml </to-view-id> </navigation-case>
- 109. Bookmarkable link 16-11-09 <h:link outcome = "product" value = "View" > <f:param name = "id" value = "#{product.id}" /> </h:link> <a href="/product.jsf?id=3">View</a>
- 111. Redirect after POST the hard way 16-11-09 FacesContext ctx = FacesContext.getCurrentInstance(); ExternalContext extCtx = ctx.getExternalContext(); String url = ctx.getApplication().getViewHandler() .getActionURL(ctx, "/product.xhtml" ) + "?id=" + getProductId(); try { extCtx.redirect(extCtx.encodeActionURL(url)); } catch (IOException ioe) { throw new FacesException(ioe); }
- 112. Redirect after POST the easier way 16-11-09 <navigation-case> <from-action> #{productBean.save} </from-action> <if> #{productBean.id != null} </if> <to-view-id> /product.xhtml </to-view-id> <redirect> <view-param> <name> id </name> <value> #{productBean.id} </value> </view-param> </redirect> </navigation-case>
- 113. Redirect after POST the best way 16-11-09 <navigation-case> <from-action> #{productBean.save} </from-action> <if> #{productBean.id != null} </if> <to-view-id> /product.xhtml </to-view-id> <redirect include-view-params = "true" /> </navigation-case>
- 115. 16-11-09 Resource handling Native resource handling, packaging and resource relocation
- 116. 16-11-09 No more “bonus” servlet!
- 118. Declarative component resources 16-11-09 @ResourceDependency ( name = "jsf.js" , library = "javax.faces" , target = "head" ) public class MyComponent extends UIOutput { ... }
- 120. 16-11-09 A third request processing scenario
- 124. 16-11-09 Model Java EE 6 component model, Bean Validation, error handling and resource loading
- 130. Simple example 16-11-09 public class Hello { public String sayHello(String name) { return "Hello, " + name; } } @Stateless public class Hello { public String sayHello(String name) { return "Hello, " + name; } } Any Managed Bean can use CDI services ...even EJBs!
- 131. Simple example 16-11-09 public class Printer { @Inject Hello hello ; public void printHello() { System.out.println( hello .sayHello( "Devoxx" )); } } @Inject defines injection point, assumes @Default qualifier
- 132. Constructor injection 16-11-09 public class Printer { private Hello hello ; @Inject public Printer(Hello hello) { this . hello = hello; } public void printHello() { System. out .println( hello .sayHello( "Devoxx" )); } } @Inject marks constructor to be called by container; arguments injected automatically
- 133. Bean EL names 16-11-09 @Named( "hello" ) public class Hello { private String name; // getters and setters not shown public void sayHello() { System. out .println( "Hello, " + name); } } @Named public class Hello { ... } @Named makes bean available to EL Name can be defaulted to simple name of class
- 134. JSF view 16-11-09 <h:inputText value = "#{hello.name}" /> <h:commandButton value = "Say Hello" action = "#{hello.sayHello}" /> Invoking a bean via EL
- 135. 16-11-09 Qualifier An annotation that lets a client choose between multiple implementations of an API at runtime
- 136. Write a qualified implementation 16-11-09 @Casual public class Hi extends Hello { public String sayHello(String name) { return "Hi, " + name; } } This second Hello bean is qualified @Casual
- 137. Using a qualifier 16-11-09 public class Printer { @Inject @Casual Hello hello ; public void printHello() { System. out .println( hello .sayHello( "Devoxx" )); } } Injects the @Casual implementation of Hello
- 141. 16-11-09 Validation Bean Validation integration, validating empty fields and multi-field validation with post-validate events
- 142. 16-11-09 One model... ...validated across multiple layers Constraints in the enterprise User String username String email
- 144. Defining constraints on the model 16-11-09 public class User { ... @NotNull @Size(min = 3, max = 25) public String getUsername() { return username ; } @NotNull @Email public String getEmail() { return email ; } }
- 145. 16-11-09 One model... ...validated across multiple layers Constraints in JSF User String username String email
- 146. Enforcing constraints in the UI 16-11-09 <h:inputText id = "username" value = "#{user.username}" /> <h:inputText id = "email" value = "#{user.email}" /> Zeroconf!
- 147. Constraining partially 16-11-09 <h:inputText id = "username" value = "#{user.username}" > <f:validateBean disabled = "true" /> </h:inputText> <f:validateBean validationGroups = "com.acme.BareMinimum" > <h:inputText id = "email" value = "#{user.email}" /> </:validateBean>
- 151. Listening for post validate 16-11-09 <h:form> <f:event type="postValidate" listener="#{minMax.validate}"/> <h:inputText id = "min" value = "#{bean.min}" binding = "#{minMax.minInput}" /> <h:inputText id = "max" value = "#{bean.max}" binding = "#{minMax.maxInput}" /> <h:commandButton value = "Submit" /> </h:form>
- 152. Validating across fields 16-11-09 @Inject FacesContext ctx ; private UIInput minInput , maxInput ; // accessors hidden public void validate () { if ( ctx .isValidationFailed()) { return ; } if ((Integer) maxInput .getValue() < (Integer) minInput .getValue()) { ctx.addMessage( maxInput .getClientId(ctx), new FacesMessage( "cannot be less than min value" )); ctx.validationFailed() ; ctx.renderResponse(); } }
- 154. 16-11-09 Error handling Exception handlers, exception events, servlet errors and the default error page
- 155. 16-11-09 The good news No more swallowed exceptions!
- 156. 16-11-09 The bad news You’re still going to get exceptions
- 158. 16-11-09 Default error page
- 161. Declarative error handling in JSF 16-11-09 <exception class = "javax.persistence.EntityNotFoundException" > <redirect view-id = "/error/404.xhtml" > <message severity = "warn" > Record not found </message> </redirect> </exception> Wouldn’t it be nice if we had...? JSF 2.next
- 163. 16-11-09 Pain relief Select items from collections, validation failed flag, API improvements, varStatus on ui:repeat, and more...
- 164. From collection to select items 16-11-09 <h:selectOneMenu value = "#{product.category}" > <f:selectItems value = " #{catalogBean.categories} " var = "cat" itemLabel = "#{cat.name}" itemValue = "#{cat}" noSelectionValue = "#{catalogBean.defaultCatalog}" /> </h:selectOneMenu> @Named public class CatalogBean { public List<Category> getCategories() { return ...; } }
- 167. 16-11-09 Community JSR-314-OPEN mailinglist, javaserverfaces-spec-public project, JCP.org and you !
- 170. 16-11-09 Creating a JCP.org profile Did you know that anyone can have a JCP.org profile? Just sign up!
- 172. 16-11-09 Becoming a JCP member Did you know that anyone can become a JCP member? Just sign the JSPA!
Hinweis der Redaktion
- We are going to have a great time this afternoon....because if the colors in that slide only get your fired up (or make your eyes bleed)....we'll, I don't know what's going to do it.In this talk we are going to be talking about progress. Specficially progress in JSF.Look, progress was a little bit of a stranger to JSF when the spec first opened. But it eventually found it's way and momentum has been steadily picking up right and plowed right through the final release of JSF 2. Now, there's been more active on the JSF development list since it became final than at any other point. We got a lot of what we wanted, but now we want more. (In fact, just creating this talk helped us identify areas for improvement). JSF 2 features were derived from community, precendent.
- The goals of this talk are to pull off on the side of the road and look at where we've been, to explain the community's role in the making of JSF 2 and how you can help shape JSF 2.next and a glimpse at some of the things are in store for JSF 2.next. You may wonder what &quot;.next&quot; is all about. We'll, at this point we are really not sure whether the next version is JSF 2.1, 2.2 or some other version, or what JSR it's going to be under. But we are committed to seeing it happen, and with urgency. JSF 2.next also happens to be the issue tracker tag designated for future issues, so it's a bit of a play on that.
- The underlying theme of this talk is collaboration and community involved. (conference theme) So before we get into the talk, we want to enourage you to feel like you are a part of it right from the beginning. Expecting you guys to speak out in a forum like this is often wishful thinking. Instead, you can interact in a way familiar to a lot of you, using twitter. I've selected the hashtag #jsf2next for you to make suggestions, ask questions or request clarification. At points during the talk, maybe not until the end, we'll parse this feedback and customize the content. That way, you'll really feel like your are involved. Even if we don't get to all the comments, it's a perfect starting point for tonight.
- So speaking of birds and feathers, there is a BOF tonight at 20:00 that will be the ideal break-out session to comlement this talk. So comment in twitter now, and if we don't get to it, then it's a conversation piece for tonight.I'd like to take this opportunity to tell you who we are.
- Primary reason I am standing here today is because of what I wrote in Seam in Action; recognized where JSF could be improved (James Cobb, who came through in the clutch to put together some colors for us to use in code snippets)You'll notice that this is a joint talk because Oracle and Red Hat. Although we work for different organization, we are collegues on the JSR-314 EG. We are also members of the broader JSF community which we represent.But it's not just about our two organizations. We stand up hear representing the JSF EG. We feel a very strong alliance in this spec, one that you can certainly be proud of as community members. A lot of people have been involved in JSF; i've done my best to identify the faces of JSF, past, present and future [Faces of JSF slide]
- We're going to break this talk up into parts, each of which one of us will be covering. Subconsciously, the topic areas sort of just fell into MVC, which is the foundation pattern of JSF. Also nicely breaks down between two halfs of this talk. First half, point, second half point. We'll do a short break in between to let you stretch your legs and brains (and to get in a few tweets).
- Let's get on with it, shall we. I'll now turn the floor over to Andy, who is going to show you how slick the view creation has become, complete with Ajax, JavaScript APIs and powerful templating.
- Point is, no special tricks
- PreRenderView event loop
- Serve resource files natively out of a Java archive
- * Emphsize the web profile - lightweight, aimed at developing “web” apps
- * We can improve on the syntax for this! f.e. make faces messages easier to add, add some syntatic sugar i.e. consider this an idea, not the canonical way to do it
- * Discuss JSF design flaw - exceptions for flow control!