Pete, is this proposal related with performance only or are there other use cases ? The only use case I can find is disabling scanning on 3rd party libraries that are embedded in the project.Antonio--On Thu, Sep 13, 2012 at 12:15 AM, Bill Shannon <bill.shannon@...> wrote:
For those of you who want a feature such as this, what problem is it
solving for you? Examples would be helpful.
Pete Muir wrote on 09/12/12 09:32:
> 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.
Software architect and Java Champion
Web site | Twitter | LinkedIn | Paris JUG | Devoxx France
[javaee-spec users] [jsr342-experts] Re: Control over what is scanned, within a jar/module