jboss-weld

I am trying to observe both the startup and shutdown events for a CDI web application. I have an ApplicationScoped bean that listens for those events: @ApplicationScoped public class PrettyfacesStartupObserver { private static final Log LOGGER = LogFactory.getLog(PrettyfacesStartupObserver.class); public PrettyfacesStartupObserver() { LOGGER.debug("\n\n\n\n\n\n\n\n\n\nconstructor"); } public void onStartup(@Observes AfterBeanDiscovery afterBeanDiscovery ) { LOGGER.debug("\n\n\n\n\n\n\n\n\n\nafter bean discover"); } public void onStartup(@Observes AfterDeploymentValidation

[ UPDATE : After discussion on the Glassfish forums/ML at http://forums.java.net/jive/thread.jspa?messageID=480532 a bug was filed against Glassfish https://glassfish.dev.java.net/issues/show_bug.cgi?id=13040 for this issue.] I'm trying to inject a local no-interface view of a @Stateless EJB into a JSF2 @Named @javax.enterprise.context.SessionScoped backing bean. The EJB is one of several that extend an abstract generic base class. Injection of "@Inject TheEJBClass varName" fails with "Unable to convert ejbRef for ejb TheEJBClass to a business object of type class my.package.name

JSR-330 dependency injection can be applied to both Java SE and Java EE environments, while JSR-299 is titled "Contexts and Dependency Injection for the Java EE platform". Except strictly Java EE-oriented features, what CDI features make sense on Java SE as well? Any examples available? Thanks! [Revised] Here's Weld on JSE. Pascal Thivent Except strictly Java EE-oriented features, what CDI features make sense on Java SE as well? Any examples available? Thanks! Well, the one mentioned in the Weld documentation: 18.4. Java SE In addition to improved integration of the Enterprise Java stack, the

I seem to be having a problem where I have an a4j:commandLink on a rich:popupPanel but the action is not firing. The xhtml looks as follows: <rich:popupPanel id="rate-panel" modal="true" height="444" width="780" top="60" show="false" onmaskclick="#{rich:component('rate-panel')}.hide()" styleClass="cs-modal"> /**Some html here**/ <a4j:commandLink immediate="false" action="#{venueScore.up}" render="rate-panel" styleClass="rate love"> <span>Love it</span> </a4j:commandLink> /**Some more html here**/ </rich:popupPanel> And the managed bean looks as follows: @Named("venueScore") @ViewScoped public

I would like to achieve this idealism : To have only 1 implementation for the JSF Bean container, like to use only Spring or Weld but not both. Currently i am using Spring for my backend, so i prefer Spring. To have only 1 annotation, to choose between @ManagedBean, @Named, @Model To be able to use all supported scopes, like @RequestScoped, @SessionScoped, @ViewScoped, @FlashScoped, maybe also @ConversationScoped The JSF Beans could be injected with spring-managed-services (The backend services), perhaps using @Inject or @Autowired So far i've been finding no best combination to achieve these

I've found lots of tutorials showing Weld code samples, but not an introductory overview. Could you please suggest an introductory article, or answer the following: What does Weld do/give you? How does it relate to Java EE 6? How would one use it in a Java EE 6 project? If one uses it in a Java EE 6 project, what is it supplanting, if anything? BalusC What does Weld do/give you? Weld is the reference implementation of the abstract JSR-299 API , which is better known as CDI, Contexts and Dependency Injection, an API which is provided through javax.enterprise.context and javax.enterprise.inject

I would like to know if the RequestScoped context is currently active in a method or not. At the moment, here is what I do : @Inject private BeanManager beanManager; public boolean isRequestScopeActive() { try { if (beanManager.getContext(RequestScoped.class).isActive()) { return true; } else { return false; } } catch (final ContextNotActiveException e) { return false; } } I think it's a bit heavy to catch a ContextNotActiveException just to know if a scope is active or not. Do you have any better way to know the state (active or not) of a context in CDI ? Yeah, the only option we have in CDI

This question already has answers here : Retaining GET request query string parameters on JSF form submit (2 answers) I'm facing the following issue: in one page, I list all users of my application and have an "edit" button for each one, which is a "GET" link with ?id=<userid> . The edit page has a <f:viewParam name="id" value="#{editUserBean.id}"/> in metadata. If I made some input mistakes and submit (I use CDI Weld Bean validation), the page is displayed again, but I've lost the ?id=... in the URL and so lose the user id of the user I'm editing. I've looked at a similar problem described in