Weld not initializing properly

前端 未结 4 1290
名媛妹妹
名媛妹妹 2021-01-12 03:42

I am setting up basic environment for learning CDI in JavaEE7. I have the following code for starting Weld. Just a startup and shutdown.

package         


        
相关标签:
4条回答
  • 2021-01-12 03:58

    Your setup is ok for learning CDI in Java SE.

    For using CDI in Java EE, you obviously need a Java EE Container, a plain old application with a main method won't do.

    Weld is simply telling you that transactions are not available (since you're not running in an EE container), so any transaction-related CDI features will be disabled.

    Dependency injection will work in your case, as long as you don't try to inject any Java EE objects or use any CDI features that require a Java EE container.

    0 讨论(0)
  • 2021-01-12 04:01

    This problem also occur even if you miss to keep beans.xml file in you test/resource/META-INF folder.\

    Make sure you are maintaining beans.xml file as its mandatory file for Context and Dependency injection.

    0 讨论(0)
  • 2021-01-12 04:04

    To set up a learning CDI environment, all you need is a CDI implementation such as the Weld reference implementation; you don't need a Java EE container.

    The easy way is to create a maven project with a dependency in pom.xml: (Make sure to create an empty or the minimal beans.xml file in META-INF directory before you run the java application. If you go for maven, you can create META-INF in the src/main/resources directory)

    <dependency>
        <groupId>org.jboss.weld.se</groupId>
        <artifactId>weld-se</artifactId>
        <version>2.3.4.Final</version>
    </dependency>
    

    Here's the application:

    public class CdiApplication {
        private Weld weld;
        private WeldContainer container;
        private BookService bookService;
    
        private void init() {
            weld = new Weld();
            container = weld.initialize();
            BookService = container.instance().select(BookService.class).get();
        }
    
        private void start() {
            Book book = bookService.createBook("My title", "My description", 23.95);
            System.out.println(book);
        }
    
        private void shutdown() {
            weld.shutdown();
        }
    
        public static void main(String[] args) {
            CdiApplication application = new CdiApplication();
            application.init();
            application.start();
            application.shutdown();
        }
    
    }
    

    The Book class:

    public class Book {   // Book is a POJO
        private String title;
        private String description;
        private double price;
        private String id;    // ISBN or ISSN
        private Date instanciationDate;
    
        public Book() {   // default constructor
    
        }
    
        public Book(String title, String description, double price) {
            this.title = title;
            this.description = description;
            this.price = price;
            // the BookService is responsible to set the id (ISBN) and date fields.
        }
    
        // setters and getters
        // toString method
    }
    

    And the BookService class to create an book and set its instanciation date and id (ISBN) using the injected NumberGenerator:

    public class BookService {
        @Inject
        private NumberGenerator numberGenerator;
    
        private Date instanciationDate;
    
        @PostConstruct
        private void setInstanciationDate() {
            instanciationDate = new Date();
        }
    
        public Book createBook(String title,
            String description, double price) {
    
            Book book = new Book(title, description, price);
            book.setId(numberGenerator.generateNumber());
            book.setDate(instanciationDate);
    
            return book;
        }
    
    }
    

    In a servlet environment, the servlet container will responsible to bootstrap the CDI, meaning that you have to deploy your "web application" on a Java EE container such as Tomcat or Wildfly.

    0 讨论(0)
  • 2021-01-12 04:16

    Running Java EE application requires an Application server (or container). This container makes your life far simple regarding the integration of different services (security, messaging, transaction, etc...) needed to run an enterprise application.

    If you don't use an application server (like you are doing in your example) you have to make this integration yourself (i.e build your own server). That's a very hard and useless task since servers exist.

    The code you show in your question is how you can use the proprietary part of Weld to start a CDI container by hand when you don't want or can use a container.

    If you read carefully Antonio's book, you'll see that on page xxxiv in section 'Download and Running the Code' it is stated that you need to deploy your code on Glassfish 4, one of the open source Java EE 7 server (the other being JBoss Wildfly)

    Appendix A of the book (page 539) describe in a very precise way how to set up your environment to run book examples and simple Java EE applications. Please follow instruction in this part and you'll see that developing and deploying Java EE 7 application si very simple.

    0 讨论(0)
提交回复
热议问题