Dan Allen

By Dan Allen

This session discloses best practices, tips and techniques and disclose inside information to save you in a pinch and maximize your use of Seam, RichFaces, JSF and Facelets.

Dan has amassed a catalog of hidden gems and lesser known facts while developing in the Seam ecosystem. This session discloses those best practices, tips and techniques and gives you inside information to save you in a pinch and maximize your use of Seam, RichFaces, JSF and Facelets. If you are a developer working with any or all of these technologies today, this session is a must see to help you find the path to success while avoiding the slippery steps.

By Dan Allen

JSR-311 (JAX-RS) is one of the simplest, most elegant of all the Java EE specifications and is showing early signs of becoming an overwhelming success. It lets you to create RESTful web services from existing Java EE components by sprinkling a handful of annotations over it. But the downside is that the resource must be a Java EE component. Seam's RESTEasy module allows you to use JAX-RS annotations on your existing Seam components, giving your web services access to the Seam container and, dually, an alternate interface to your Seam application.

In this talk, you learn how you can use your Seam components as REST resources using the Seam RESTEasy module. The most obvious benefit is that you can create RESTful web services using a Seam component and get access to full Seam injection, security, persistence management, and so on. You almost forget that Seam eliminates the configuration required to add JAX-RS to your application. You'll be enthralled by the module's innovative approach to doing CRUD over REST that mimics Seam's CRUD framework for JSF-based UIs. Finally, you learn about some nice extras that Seam provides such as exception handling and integration with Seam security.

By Dan Allen

Learn how Seam's security can protect your application throughout the development life cycle, from simple authentication to fine-grained, rule-based security restrictions.

Security is the cornerstone of your application's integrity and, therefore, it should be a key component of any enterprise framework. And you'd rather the complexity be confined to the security rules, not contributed by the security framework itself.

Seam's security module is a central component of the Seam framework and offers a significantly simpler alternative to the monolithic and complex Java Authentication and Authorization Service (JAAS) in Java EE. In this talk, you learn how Seam Security allows you to evolve the security model of your application over time, keeping inline with the development cycle.

The talk starts you off with a very simple configuration that applies a security blanket over the application to keep out guests and establish a basic identity for the user. Then you mature the security infrastructure of the application gradually by adopting Seam's declarative approach to authentication or defining fine-grained authorization rules that enforce contextual restrictions at the level of database records, database fields, object fields and UI fragments.

You are introduced to the numerous authorization styles that Seam supports ranging from binary, role-based, rule-based (Drools), and ACLs. Examples are presented to help you differentiate the four styles of authorization and when it's appropriate to use each one. In the process, you learn to appreciate that Seam's authorization is able to take the context of the restriction into account, a feature than many security frameworks overlook.

By the end of the talk, you will be intimately familiar with Seam's security module and be able to use it to enforce advanced security rules in your application you never thought possible.

By Dan Allen

This talk introduces JSR-299: Contexts and Dependency Injection for the Java EE platform (CDI), the new Java standard for dependency injection and contextual lifecycle management. The talk covers the core programming model, explains its relationship to EJB 3.1 and JSF 2.0, and clarifies how it unifies and enhances the Java EE platform as a whole (extending to JPA, JAX-RS and JMS). You are then introduced to Weld, the JSR-299 reference implementation, and its servlet container extension. Finally, we look ahead at how a modularized Seam 3 ties into this new foundation as a set of portable CDI extensions, previewing several examples.

JSR-299: Contexts and Dependency Injection for the Java EE platform (CDI) is an elegant set of new services for Java that draws upon ideas from popular frameworks such as Seam and Guice and hooks into all the major specifications in the platform, including JavaServer Faces (JSF) 2.0, Enterprise Java Beans (EJB) 3.1, the Java Persistence API (JPA) 2.0 and JAX-RS 1.1. While many of the features provided by CDI--dependency injection, contextual lifecycle, configuration, interception, event notification--are familiar, the innovative use of meta-annotations is uniquely expressive and typesafe. This talk emphasizes the value in this approach.

Seam is a powerful open source development platform for building rich Internet applications in Java. Seam 3 is built on CDI and integrates technologies such as Java Persistence (JPA 2.0), Business Process Management (jBPM), Wicket, PDF and Excel reporting, Security and email into a unified full-stack solution, complete with sophisticated tooling.

In this discussion, Dan will talk about upcoming developments in Java EE 6 including CDI 1.0 and JSF 2.0 and how they set the foundation for Seam 3. This is a great opportunity to learn about how Red Hat is building on this new revision of the Java EE platform.

By Dan Allen

This presentation will provide an in-depth introduction to many of the new JSF 2.0 features and will ask of each: Is the currently specified solution sufficient? We'll also consider whether other concerns (paper cuts) have been overlooked?

The JSF 2.0 specification (JSR-314) addresses a substantial number of long standing pain points that JSF users have just come to accept as a hard knock life (or death by 1000 paper cuts). At last, JSF is a true contender amongst web frameworks. Now that the specification final, it's time to take a step back, evaluate the results and look ahead to JSF 2.1.

Here's a partial list of the features we'll be covering:

• State saving: We'll introduce the new partial state saving solution in JSF 2.0 and consider whether additional utilities are needed for stricly stateless use cases.
• GET support: At long last, JSF now supports GET request processing in the form of bookmarkable URLs and request parameter binding. But how does it measure up to frameworks that accept REST-style URLs?
• Validation: Integration with JSR-303: Bean Validation changes the data validation landscape. We'll examine how far it stretches and whether it can handle that elusive multi-component validation use case.
• Ajax: JSF 2.0 finally delivers Ajax support! We'll survey this new functionality and consider just how far it goes to allowing developers to forget about the tedium of JavaScript, and how well it accomodates custom JavaScript when it's warranted.
• Facelets: The marriage between JSF and JSP was never a good one. Facelets stood in as the surrogate view handler for JSF and arguably saved the framework. Now it's part of the specification and also got it's long overdue update. But is there still room for this templating solution to improve?

While this presentation effectively provides an overview of the JSF 2.0 specification, the underlying goal of this session is to serve as an outreach to identify outstanding recommendations for making the framework more pleasant and productive to use and to give members of the JSF community the invitation to participate in the improvement of the JSF platform. As such, attendees are encouraged to bring their own concerns and suggestions to the table.

Whether you are a new JSF user who wants to find out more about the latest developments in the specification or an old hat with an issue or two on your mind, this session has something to offer you!