Dan Allen

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

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

Unit tests and mocks can only take you so far. Eventually, you'll want to see how your components behave in the real runtime environment, a style of testing referred to as integration testing. This talk introduces Arquillian, an extension for TestNG and JUnit that can be used to validate the behavior of managed and enterprise beans or POJOs that rely on enterprise services just as easily as writing a unit test. Attend this talk to learn how to do real Java EE testing.

Arquillian is an extension for TestNG and JUnit that allows the developer to validate the behavior of managed and enterprise beans or POJOs that rely on enterprise services just as easily as writing a basic unit test. You can liken Arquillian to a modern version of Cargo, though its potential extends much further.

Using the fluent API provided by ShrinkWrap, groups of tests are packaged as Java EE archives, giving the developer fine-grained control over which resources are available to be tested. The test archives are then individually deployed and executed inside a pluggable remote or embedded Java EE container or a bootstrapped CDI environment. A RPC-style (or local, if applicable) communication between the test runner and the environment negotiates which tests are executed and reports back the results. This means two things for the developer: 1) You develop and execute Arquillian tests just like you would a regular unit test and 2) The environment in which you run the tests can be easily swapped...or you can use each one in turn.

Writing a test for a real business object should not create pause. You should be able to write "integration" tests just like you would test a calculator class. Arquillian and ShrinkWrap partner to give you that experience.