Studying JSR-299, I read section 5.1 of the Weld reference which explains开发者_开发知识库 how scopes work in CDI. Apparently, context is a concept closely related to scope. The difference is not clea
I rode that is recommended to use CDI beans as backing beans instead of JSF managed beans. So i decided to create a little example, to understand how it works, for a @RequestScopedBean:
Consider the following request-scoped CDI bean: @RequestScoped public class RequestScopedBean { // ... } Now, I inject it in a application-scoped bean:
i have a strange behaviour i\'m seeing that if the user access to session bean from two different browser, the istance of session bean is the same.In my opinion this is an unespected behaviour.
I\'m working on a Java EE application, primarily JAX-RS with a JSF admin console, that uses CDI/Weld for dependency injection with javax.enterprise.context.ApplicationScoped objects. Minor debugging i
I have been tinkering around with ui:include lately and have found it to be fairly quirky in many of its behaviors.After a some testing, it seems to me like these quirks have to do with issues go back
I\'m having trouble using dependency injection (with CDI/Weld) within libraries used in a war when deploying on Glassfish 3.1. I have two libraries, say:
Can CDI inject EJB references in my remote EJB client? Actually I\'ve a JUnit test case that runs locally on my system and access a EJB running on a standalone JBoss AS.开发者_运维技巧 I\'m currentl
I just realized that my wizard component forgets the steps that lay in the past as I\'m using a @RequestScoped wizard backing bean. Using @SessionScoped will work but is ugly.
I\'m using a CDI session scoped bean to hold user related information (His user entity bean, credential, etc). I have a save method for everytime a user changes his info (like email, password, etc).
加载中,请稍侯......