Recommended
More Related Content
Similar to 2015 UJUG, JSF 2.3 portion
Similar to 2015 UJUG, JSF 2.3 portion (20)
Recently uploaded
Recently uploaded (20)
2015 UJUG, JSF 2.3 portion
- 1. JSF 2.3 Manfred Riem (@mnriem) Oracle Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |
- 2. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. M
- 3. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | • Tie up the loose ends – Specification clarifications – CDI alignment • Ease of use e.g. @Inject FacesContext • @Inject into Validators, Converters, etc. – HtmlInputHidden is ClientBehaviorHolder • Small scale new features • JSON ajax component rendering • Stateless enhancements • GET enhancements • Adopt-a-JSR support JSF 2.3 in Java EE 8 Two feature drivers, each with their own agenda M
- 4. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | JSF 2.3 Small Scale New Features • Ajax method invocation – A Faces request – Not specific to a view – Is specific to a ClientWindow – Returns results in JSON • Multi-component validation • FacesEvent direct access to FacesContext M
- 5. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Demos • Switching gears and showing you where we are at!
- 6. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Questions? • Ask them now • Talk to me afterwards
- 7. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.
Editor's Notes
- This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template. One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy To learn more about this policy, e-mail: Revrec-americasiebc_us@oracle.com For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information. http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
- This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template. One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy To learn more about this policy, e-mail: Revrec-americasiebc_us@oracle.com For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information. http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.