On Tue, 2008-11-11 at 13:23 +0100, Ales Justin wrote:
Instead of excluding all of our deploy/ deployments,
which of them should actually be scanned for annotations?
A better approach would be to have jboss deployment
descriptor (an attachment) that specifies which parts of the
deployment (classpath) you scan.
For javaee deployments this would be populated from the
relevant dds, i.e. ejb-jar.xml and web.xml
according the rules from the spec.
For anything else, we ignore scanning unless this
deployment descriptor says to do it.
i.e. sar files won't be scanned unless you say
to do so by adding the new dds.
Ales Justin wrote:
>> And the vast majority of the annotation scanning comes from looking at
>> jbossweb.sar (with all the jars it contains).
>>
>> So not much has changed since last time I posted on this. :-(
>
> I'll add a set of excluded files we don't want to scan,
> jbossweb.sar being one of them. ;-)
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development --
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx