users@javaee-spec.java.net

[javaee-spec users] [jsr342-experts] Control over what is scanned, within a jar/module

From: Pete Muir <pmuir_at_bleepbleep.org.uk>
Date: Wed, 12 Sep 2012 17:32:00 +0100

All

The CDI EG is considering standardizing fine-grained control over what classes within a jar module.

The proposal today is to take the xml we defined in Weld as a starting point http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html#d0e5767 and standardize it, making any improvements needed on the way.

A number of CDI EG members have suggested that it would be useful to standardize this not only for CDI, but for all Java EE specs, allowing a user to control, from one deployment descriptor (e.g. scan.xml) what is / isn't scanned for all technologies in Java EE.

 I know David Blevins has a similar proposal, somewhere, but not sure where.

I wanted to raise this issue here, before the CDI EG goes off and does this on it's own.

WDYT?

Pete