I have a project (EJB 3.0, packaged as EAR) with a view (JSF 2.0) and persistence (JPA 2.0, Hibernate) layer. To avoid the lazy initialization support and other issues I tried to introduce a Seam Mana
I am trying seam-wicket with embedded Jetty 6.1.26, Weld 1.1.1, seam-wicket 3.0.0, Wicket 1.4.17 After I fixed seam-wicket bug which prevents BeanManager being found (JNDI does not work, needs to pul
I am new to Arquillian and want to get some basic testing working (inject a bean and assert it does something).
First of all let me state, that the following code example worked just fine in GF 3.0.1. The troubles started when we switched to GF 3.1.
I\'m currently experimenting a little with Apache MyFaces CODI. I managed to create a simple working Typesafe-Navigation using @Page and an action Method which returns a Class.
I\'m trying to do simple thing. Inject qualified String (or File) in CDI. So I have a qualifier: @Retention(RetentionPolicy.RUNTIME)
I\'m guessing that if I have 6 requestscoped beans, only those referenced by the current view ( 开发者_运维百科for instance by using #{foo.bar}) are instantiated. Is that assumption correct? In that c
Im currently using : Apache tomcat 7 JBoss Weld servlet 1.0.1-Final empty beans.xml <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> in the web.xml
I\'m developing a JAVA EE 6 app. I\'m using CDI extensively, My question is, are @Inject and @Produces the same as @In and @Out for Seam? Are @In and @Out annotations still used now that we开发者_如何
I\'m working on a project where I want to use Interceptors to log usage of a ManagedBean. As I read in the specs and in many examples it should be possible with the current CDI implementations. The co
加载中,请稍侯......