[
http://jira.jboss.com/jira/browse/JBSEAM-1342?page=comments#action_12375579 ]
Stuart Douglas commented on JBSEAM-1342:
----------------------------------------
How about this:
Reduce the scanners responsibility to simply enumerating all files, rather than calling
handleItem for each file.
When the scanner is done a different class processes them, e.g. have a class to process
the java components etc.
This file information should be made available to components through the use of a built in
application scoped component. e.g.
<component class="org.jboss.seam...." name="myFileInformation"
/>
This built in component could then also provide helper methods to make it easier for the
end user e.g.
Set<Class> getClassesWithAnnotation(Annotation a); //gets seam and groovy classes
Set<String> getFilesThatMatchPattern(String pattern);
Set<Component> getGetAllComponents();
Generic Scanner usability
-------------------------
Key: JBSEAM-1342
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1342
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 1.2.1.GA
Reporter: Frank Cornelis
Assigned To: Gavin King
Fix For: 2.0.1.GA
Attachments: Scanner-public-handleItem.patch
Original Estimate: 5 minutes
Remaining Estimate: 5 minutes
In our project we would like to use the JBoss Seam Scanner class to browse over our EJB
classes in search for our custom @Config annotations (see
http://cup-of-java.blogspot.com/). Unfortunately the handleItem method on the Scanner
class is only package visible. This prevents generic reusability of this really powerful
Scanner class. Could you guys make the handleItem method public?
Thanks,
Frank.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira