weld-dev October 2010

weld-dev@lists.jboss.org

14 participants
14 discussions

by Dan Allen

I recognize this is an edge case, but I can see value in having @EJB injection capability when using Weld Servlet in a pre-Java EE 6 container. You could go about it at least two ways: 1. provide a portable extension that satisfies the @EJB annotation on a managed bean field 2. implement Weld's EjbServices #1 would be a great demo of a portable extension, but the shortcoming is that it's only a connector between a managed bean and an EJB. You would have to do quite a lot of work to give the EJB CDI services. #2 would be pretty easy since you could off-load all the work of #1 back to Weld. The problem is that the Weld Listener doesn't provide any hooks (that I can see) to register services before it starts the Weld container. I was imagining something like a service-provider approach so you can shove the EjbServices implementation (+ family) into the deployment classpath. Can we add that feature? We're really just a small step away from giving people access to CDI in pre-Java EE 6 containers. And there are a lot of people on those containers and will be for quite some time. -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen

14 years, 1 month

2
1
0 / 0

registering the Weld Servlet listener in a web.xml fragment or TLD

by Dan Allen

Instead of making the developer add the Weld Servle listener in their web.xml when using weld-servlet, might we consider registering it for them automatically but including it in a web.xml fragment or TLD that's bundled in weld-servlet.jar? The benefit of using the TLD is that it would work in pre-Servlet 3.0 environments. META-INF/web-fragment.xml <web-fragment xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-fragment_3_0.xsd" version="3.0"> <listener> <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> </listener> </web-fragment> META-INF/weld.tld <taglib xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_0.xsd" version="2.0"> <description> An empty tag library that registers a listener to bootstrap Weld in a Servlet container. </description> <tlib-version>1.0</tlib-version> <short-name>w</short-name> <uri>http://jboss.org/weld</uri>  <listener> <listener-class>org.jboss.weld.environment.servlet.Listener</listener-class> </listener> </taglib> Btw, we are already including other automatic configurations, such as a JSF phase listener and view handler (META-INF/faces-config.xml). Worthy of a JIRA? -Dan -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen

14 years, 2 months

3
4
0 / 0

diigo group for CDI

by Dan Allen

I created a diigo group to track CDI articles. We'll see where it goes. http://groups.diigo.com/group/cdi-tech-hub The first article I posted is a great writeup by Adam Bien about the seamless relationship between CDI and EJB, one of the crown achievements of the CDI spec. http://www.oracle.com/technetwork/articles/java/ejb-3-1-175064.html This group complement's the group Pete created for tracking CDI extension articles. http://groups.diigo.com/group/cdi-extensions I think the first will focus on core CDI and Java EE stuff, whereas the second will focus on how to use the portable extension feature. Again, we'll see how it goes having separate groups. -Dan p.s. diigo is like a cooler delicious (social bookmarks) -- Dan Allen Principal Software Engineer, Red Hat | Author of Seam in Action Registered Linux User #231597 http://mojavelinux.com http://mojavelinux.com/seaminaction http://www.google.com/profiles/dan.j.allen

14 years, 2 months

1
0
0 / 0

Invalid url Patterns for class org.jboss.weld.tests.scope.RemoteClient

by Sreekanth

Hi, I am running the core tests from the workspace against glassfish.I have these question related to 2 tests. In the test, org.jboss.weld.tests.scope.RemoteScopeTest, there is a servlet by name RemoteClient using the annotation "@WebServlet("*")". In the test resource.EMFFactoryTest, there are 3 servlets EMFConsumerTest1, EMFConsumerTest2, EMFConsumerTest3 which uses the annotation @WebServlet("emfconsumer") with out a leading "/" . Are these 2 test cases valid with respect to servlet specification?I guess these need to be rectified.Please comment. -- Thanks, Sreekanth

14 years, 2 months

4
9
0 / 0

← Newer
1
2
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-dev October 2010