Fantastic JBUG munich event with Pete Muir ( JSR 299 )

The evening was as always excellent by the JBUG Munich.




Pete gave a talk about the new JSR 299 - Contexts and Dependency and Dependency Injection for Java EE. Even though the name of the JSR 299 is very long, Pete started with some backgrounds of this JSR, about loose coupling with events, interceptors and decorators and then he explained which extras will be provided by Web Beans (Tomcat/Jetty support, Java SE, OSGI Containers, ..) and also about some features which can be used in any JSR299 Env. (Seam 2 bridge, Spring bridge, and Wicket support) and He also talked about the future of SEAM 3 and then he jumped into the concepts und status for the first release of the Web Beans RI.
If you want to know more about the presentation, here is the slide of the JSR 299 C & D & DI.

Best.

JBUG Munich meets Pete Muir with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM)

If you leave in Munich and you are a Java and JBoss Frameworks fan, then do not miss Peter Muir by the JBoss User Group München with JSR-299 - Contexts and Dependency Injection for Java EE (06.07.09 at 19:00 PM).

Here the abstract:

JSR-299: Contexts and Dependency Injection for Java EE is an elegant set of new services for Java that draws upon ideas from JBoss Seam and Google Guice. While many of the features provided (dependency injection, contextual lifecycle, configuration, interception, event notification) are familiar, the innovative use of meta-annotations is uniquely expressive and typesafe.

In this session, Pete will introduce how JSR-299: Contexts and Dependency Injection for Java EE enhances the Java EE programming model step by step, and describe how it integrates with existing other Java EE technologies, such as EJB 3.0, JSF, and Servlets.

For more information, please take a look at the JBUGM site. And thanks to our sponsors innoQ Deutschland GmbH, JBoss a division of Red Hat and mgm technology partners.

Bests

Constantly used Key Words to indicate Requirement Levels

During the analyze and design of a product, Business Champions and Architects use some words (Key Words) to indicate some requirement levels in specification. Their meaning is well-defined by the memo of S. Bradner, Key Words for use in RFCs to Indicate Requirement Levels. But here is a summary:

• MUST ~ REQUIRED ~ SHALL - Is an absolute requirement.
• SHOULD ~ RECOMMENDED - It is strongly suggested to follow the instructions, but deviation is not excluded, if there is a reason.
• MAY ~ CAN ~ OPTIONAL - System is furthermore interoperable, if an optional item is missed

Bests.