Context and Dependency Injection
Upcoming SlideShare
Loading in...5

Context and Dependency Injection



A Cocktail of Guice and Seam, the missing ingredients for Java EE 6

A Cocktail of Guice and Seam, the missing ingredients for Java EE 6



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Context and Dependency Injection Context and Dependency Injection Presentation Transcript

  • Context &Dependency InjectionA Cocktail of Guice and Seam, themissing ingredients for Java EE 6 Werner Keil 21/04/2011
  • Without Dependency InjectionExplicit Constructorclass Stopwatch { final TimeSource timeSource; Stopwatch () { timeSource = new AtomicClock(...); } void start() { ... } long stop() { ... }} 2
  • Without Dependency InjectionUsing a Factoryclass Stopwatch { final TimeSource timeSource; Stopwatch () { timeSource = DefaultTimeSource.getInstance(); } void start() { ... } long stop() { ... }} Somewhat like in 3
  • Without Dependency InjectionMock Datavoid testStopwatch() { TimeSource original = DTS.getInstance(); DefaultTimeSource.setInstance(new MockTimeSource()); try { Stopwatch sw = new Stopwatch(); ... } finally { DTS.setInstance(original); }} 4
  • With Dependency Injection@Injectclass Stopwatch { final TimeSource timeSource; @Inject Stopwatch(TimeSource timeSource) { this.timeSource = TimeSource; } void start() { ... } long stop() { ... } } 5
  • JSR-330Definition @Inject  Identifies injectable constructors, methods, and fields . This works for both static and non-static elements. @Qualifier  Identifies qualifier annotations to declare binding types of your API @Named  A name (string) based qualifier  Others may be declared application - or 6
  • JSR-330Implementation @Provider  Provides instances of an (injectable) type. Allows  Retrieving multiple instances.  Lazy or optional retrieval of an instance.  Breaking circular dependencies.  Abstracting scope @Singleton  Identifies a type that the injector only instantiates once.  See the well-known Design 7
  • 8
  • JSR-330Configuration1. Minimal but usable API: A small API surface seems more important than making it as convenient as possible for clients. There are only two methods in the proposed API that could be considered convenience, added because they seemed to pull their weight  InjectionConfigurer.inject and InjectionSpec.inject(Object)2. Builder-style API: so-called "fluent APIs“ • Open to other 9
  • JSR-330Configuration (2)3. Abstract classes instead of interfaces: 2 main types  (InjectionConfigurer and InjectionSpec) are abstract classes instead of interfaces.  This allows new methods to be added later in a binary- compatible way.4. Separate configuration API • The API does not specify how an instance of InjectionConfigurer is obtained. • Otherwise we have to standardize the injector API itself, something outside of the stated scope of 10
  • JSR-330Configuration (3)5. Names are different from Guices configuration API: This is mostly to keep this separate from existing configuration APIs, but also so that new concepts (like "Binding") dont have to be 11
  • More about JSR-330, see or 12
  • Formerly known as WebBeans… 13
  • JSR-299Services The lifecycle and interactions of stateful components bound to well-defined lifecycle contexts, where the set of contexts is extensible A sophisticated, type safe dependency injection mechanism, including a facility for choosing between various components that implement the same Java interface at deployment time An event notification 14
  • JSR-299Services (2) Integration with the Unified Expression Language (EL), allowing any component to be used directly within a JSF or JSP page The ability to decorate injected components A web conversation context in addition to the three standard web contexts defined by the Java Servlets specification An SPI allowing portable extensions to integrate cleanly with the Java EE 15
  • • Sophisticated,• Type Safe,• Dependency Injection,… 16
  • IN MEMORIAMPietro Ferrero Jr. 11 September 1963 – 18 April 17
  • JSR-299Bean Attributes A (nonempty) set of bean types A (nonempty) set of bindings A scope A deployment type Optionally, a bean EL name A set of interceptor bindings A bean 18
  • JSR-299Context• A custom implementation of Context may be associated with a scope type by calling BeanManager.addContext().public void addContext(Context context); 19
  • JSR-299Context (2)• BeanManager.getContext() retrieves an active context object associated with the a given scope:public Context getContext(Class<? extends Annotation> scopeType);→ Context used in a broader meaning than some other parts of Java (Enterprise) 20
  • JSR-299Restricted Instantiation@SessionScopedpublic class PaymentStrategyProducer { private PaymentStrategyType paymentStrategyType; public void setPaymentStrategyType( PaymentStrategyType type) { paymentStrategyType = type; } 21
  • JSR-299Restricted Instantiation (2)@Produces PaymentStrategy getPaymentStrategy(@CreditCard PaymentStrategy creditCard,@Cheque PaymentStrategy cheque,@Online PaymentStrategy online) { switch (paymentStrategyType) { case CREDIT_CARD: return creditCard; case CHEQUE: return cheque;[…] 22
  • JSR-299Restricted Instantiation (3)[…] case ONLINE: return online; default: throw new IllegalStateException(); } }} 23
  • JSR-299Event Observer• Then the following observer method will always be notified of the event:• public void afterLogin(@Observes LoggedInEvent event) { ... }• Whereas this observer method may or may not be notified, depending upon the value of user.getRole():• public void afterAdminLogin(@Observes @Role("admin") LoggedInEvent event) { ... } 24
  • JSR-299Event Binding• As elsewhere, binding types may have annotation members:@BindingType@Target(PARAMETER)@Retention(RUNTIME)public @interface Role { String value();} 25
  • JSR-299Event Binding (2) Actually @Role could extend @Named from JSR-330 JSRs here potentially not consequently streamlined…? 26
  • JSR-299Portable Extensionspublic interface Bean<T>extends Contextual<T> { public Set<Type> getTypes(); public Set<Annotation> getBindings(); public Class<? extends Annotation> getScopeType(); 27
  • JSR-299Portable Extensions (2) public Class<? extends Annotation> getDeploymentType(); public String getName(); public Class<?> getBeanClass(); public boolean isNullable();public Set<InjectionPoint> getInjectionPoints();} 28
  • 31
  • More about JSR-299, see JCP or opersummit/sessions.html#session66 (cancelled ;-/) 32
  • Further Reading • • Java™ EE Patterns and Best Practices / 33
  • Thank you! Contact & Questions Twitter 34