User development,
A new message was posted in the thread "another annotation scanner
requirement":
http://community.jboss.org/message/518894#518894
Author : Ales Justin
Profile :
http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
Well, I want something usable now so I can finish my resteasy
integration. I'd be willing to both patch whatever is going to be in M2 and expand on
whatever is going to be there in the future.
For M2 you'll still need to do it
the old/slow way.
For M3 I'll make sure we already have some working more-usable/more-optimal solution.
Porting your lookup mechanism afterwards should be easy.
Also, you need facilities to state that a jar/deployment
shouldnt' be scanned. My bet is that most of the jar files that come with JBoss
won't need to be scanned.
This already exists, in various forms.
* empty
http://www.jboss.org/community/docs/DOC-13178
* list jar/deployment in excluded list:
http://anonsvn.jboss.org/repos/jbossas/trunk/server/src/etc/deployers/met...
If either of these two mechanisms is up-to-date wrt our jars/deployments,
we shouldn't be scanning anything already at boot time.
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/518894#518894