[seam-dev] Identifying which jars contains seam/cdi extensions and programmatic extensions ?

[Dan Allen]

On Fri, Mar 25, 2011 at 14:22, Alexey Kazakov <akazakov at exadel.com> wrote:

> We are going to support Seam 3 extensions (such as @Veto, generic, ...)
> so we don't need to have some extra meta for such beans.
> We are going to look at
> META-INF/services/javax.enterprise.inject.spi.Extension and handle all
> the known extensions properly.
> But is it enough for Seam 3? For instance for weld we had to scan
> *weld*.jar's in a special way since they don't have beans.xml. But some
> of those beans we should not load (for example we don't load
> weld-extensions*.jar). How we supposed to recognize such beans in design
> time? Is there any documented way to do it?
>

Only some trial and error will truly reveal, but Seam 3 should be very
straightforward for the most prominent APIs.

The best way to find out is to take some of these examples out of the Seam 3
distribution and open them up and see where the yellow squiggly lines are
located. Seam booking is one good example, but there are others.

I think over the next month or so, we'll have a lot more feedback for the
tools team. We'll keep our eyes open for tooling opportunities.

Btw, one on my mind that I mentioned to Max the other day is injection of
UserTransaction. This is mandated by the CDI spec, so it should be
recognized. Currently it isn't in the Seam booking example (at least in
my relatively recent milestone installation).

-Dan

-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110326/bef65542/attachment.html