跳至主要内容

CDI 2.0: Java SE support

Java SE support

The Java SE support in weld is now standardized, it is useful when you want to get CDI support out of Java EE application servers.
Given a simple CDI bean.
@Named
@ApplicationScoped
public class Greeter {

    public void say(String name) {
        System.out.println("Hi, " + name);
    }
}
You can start CDI SeContainer like this.
 SeContainerInitializer initializer = SeContainerInitializer.newInstance();
try (SeContainer container = initializer.initialize()) {
 assertTrue(container.isRunning());
 Set<Bean<?>> greeters = container.getBeanManager().getBeans("greeter");
 assertTrue(greeters.size() == 1);
}
There is a try-resources statement, SeContainer is a AutoClosable and can be closed automaticially at the end.
To bootstrap CDI container for Java SE, you have to add the following dependencies in project.
<dependency>
 <groupId>org.jboss.weld.se</groupId>
 <artifactId>weld-se-shaded</artifactId>
 <version>3.0.0.Final</version>
</dependency>
Weld also provides some simple APIs to bootstrap a CDI container.
Weld weld = new Weld();

try (WeldContainer container = weld.initialize()) {
 Greeter greeter = container.select(Greeter.class).get();
 assertTrue(greeter != null);
}
You can utilize Weld APIs to modify beans in the CDI container lifecycle.
@Test(expected = UnsatisfiedResolutionException.class)
public void bootWeldSeContainer() {
 Extension testExtension = ContainerLifecycleObserver.extensionBuilder()
  .add(afterBeanDiscovery((e) -> System.out.println("Bean discovery completed!")))
  .add(processAnnotatedType().notify((e) -> {
   if (e.getAnnotatedType().getJavaClass().getName().startsWith("com.hantsylab")) {
    e.veto();
   }
  }))
  .build();
 try (WeldContainer container = new Weld().addExtension(testExtension).initialize()) {
  Greeter greeter = container.select(Greeter.class).get();
  //assertTrue(greeter == null);
 }
}
In the above codes, it vetoes Greeter bean in processAnnotatedType phase, the later bean select operation will cause an exception UnsatisfiedResolutionException thrown.
Grab the source codes from my github account, and have a try.

发表评论

此博客中的热门博文

JPA 2.1: Attribute Converter

JPA 2.1: Attribute Converter If you are using Hibernate, and want a customized type is supported in your Entity class, you could have to write a custom Hibernate Type. JPA 2.1 brings a new feature named attribute converter, which can help you convert your custom class type to JPA supported type. Create an Entity Reuse thePostentity class as example. @Entity @Table(name="POSTS") public class Post implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue(strategy = GenerationType.AUTO) @Column(name="ID") private Long id; @Column(name="TITLE") private String title; @Column(name="BODY") private String body; @Temporal(javax.persistence.TemporalType.DATE) @Column(name="CREATED") private Date created; @Column(name="TAGS") private List<String> tags=new ArrayList<>(); } Create an attribute converter In this example…

Build a Reactive application with Angular 5 and Spring Boot 2.0

I have created a post to describe Reactive programming supports in Spring 5 and its subprojects, all codes of this article are updated the latest Spring 5 RELEASE, check spring-reactive-sample under my Github account.
In this post, I will create a simple blog system, including:
A user can sign in and sign out.An authenticated user can create a post.An authenticated user can update a post.Only the user who has ADMIN role can delete a post.All users(including anonymous users) can view post list and post details.An authenticated user can add his comments to a certain post. The backend will be built with the latest Spring 5 reactive stack, including:
Spring Boot 2.0, at the moment the latest version is 2.0.0.M7Spring Data MongoDB supports reactive operations for MongoDBSpring Session adds reactive support for WebSessionSpring Security 5 aligns with Spring 5 reactive stack The frontend is an Angular based SPA and it will be generated by Angular CLI.
The source code is hosted on Github, …

Auditing with Hibernate Envers

Auditing with Hibernate Envers The approaches provided in JPA lifecyle hook and Spring Data auditing only track the creation and last modification info of an Entity, but all the modification history are not tracked. Hibernate Envers fills the blank table. Since Hibernate 3.5, Envers is part of Hibernate core project. Configuration Configure Hibernate Envers in your project is very simple, just need to addhibernate-enversas project dependency. <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-envers</artifactId> </dependency> Done. No need extra Event listeners configuration as the early version. Basic Usage Hibernate Envers provides a simple@Auditedannotation, you can place it on an Entity class or property of an Entity. @Audited private String description; If@Auditedannotation is placed on a property, this property can be tracked.