Is there a special deployer API for scanning for classes that extend or implement a specific interface?

On Fri, Jun 11, 2010 at 1:38 AM, Bill Burke <bburke(a)redhat.com&gt; wrote: > Is there a special deployer API for scanning for classes that extend or > implement a specific interface? Yes, the web scanning plugin does that, you can use it in a deployer. import org.jboss.scanning.web.spi.ResourcesIndex; addInput(ResourcesIndex.class); ResourcesIndex ri = unit.getAttachment(ResourcesIndex.class); VirtualFile classpathItem; Class<?> type; Set classes = ri.getInheritedClasses(classpathItem, type); I did not verify the actual results yet. For David, I use it for SCI, which is a Servlet 3 feature, and having to use it with type Object is also a possibility. Rémy _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

On Fri, Jun 11, 2010 at 5:35 PM, Bill Burke <bburke(a)redhat.com&gt; wrote: > Hmmm, where you get the classpathItem from then? AnnotationIndex > doesn't require for you to provide this info. It's just a regular VirtualFile to the JAR or exploded folder. For the classpath you could do: List<VirtualFile> classpath = (VFSDeploymentUnit) unit.getClassPath(); Rémy _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I also have written a scanner plugin that indexes classes that implement anntotations that are annotated with: i.e. @Path public interface MyResource {} public class MyResourceImpl implements MyResource {} Set<String> classes = interfaceIndex.getAnntoationIndex(Path.class.getName()) Ales Justin wrote: > I've fixed this in scanning trunk, so you don't need the url anymore. > If null, the whole deployment unit's owning classpath will be checked. > > For the moment you can use the scanning trunk's snapshot - the api is still the same, > and I'll try to do new release asap -- need to fix some CL & Deployers issue before doing the whole cycle. > > > On Jun 11, 2010, at 10:46 PM, Rémy Maucherat wrote: > >> On Fri, Jun 11, 2010 at 5:35 PM, Bill Burke <bburke(a)redhat.com&gt; wrote: >>> Hmmm, where you get the classpathItem from then? AnnotationIndex >>> doesn't require for you to provide this info. >> It's just a regular VirtualFile to the JAR or exploded folder. For the >> classpath you could do: >> List<VirtualFile> classpath = (VFSDeploymentUnit) unit.getClassPath(); >> >> Rémy >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

No, not annotation on anntation. Please look at the example below again.

JAX-RS services are identified via the @Path annotation, just like EJB's are identified with @Stateless or @Stateful. The different is that the @Path annotation can either be on the class, or an implemented interface. This does not exist in the scanner framework ATM, AFAICT.

Ales Justin wrote: > You can already do this with existing indexes. > > AnnIndex ai = ...; > Set<Class> annClasses = ai.classHasAnnotation(Path.class.getName()); > > HierarchyIndex hi = ...; > for (Class annClass : annClasses) > { > Set<Class> hieClasses - hi.getSuperTypes(annClass); > ... > } > > Actually, you're in contradiction here: > * "classes that implement anntotations that are annotated with" > * MyResource is not an annotation > > For "annotation on annotation" one could simply use the AI twice. > > On Jun 14, 2010, at 3:43 PM, Bill Burke wrote: > >> I also have written a scanner plugin that indexes classes that implement >> anntotations that are annotated with: >> >> i.e. >> >> @Path >> public interface MyResource {} >> >> public class MyResourceImpl implements MyResource {} >> >> >> Set<String> classes = >> interfaceIndex.getAnntoationIndex(Path.class.getName()) >> >> >> >> Ales Justin wrote: >>> I've fixed this in scanning trunk, so you don't need the url anymore. >>> If null, the whole deployment unit's owning classpath will be checked. >>> >>> For the moment you can use the scanning trunk's snapshot - the api is still the same, >>> and I'll try to do new release asap -- need to fix some CL & Deployers issue before doing the whole cycle. >>> >>> >>> On Jun 11, 2010, at 10:46 PM, Rémy Maucherat wrote: >>> >>>> On Fri, Jun 11, 2010 at 5:35 PM, Bill Burke <bburke(a)redhat.com&gt; wrote: >>>>> Hmmm, where you get the classpathItem from then? AnnotationIndex >>>>> doesn't require for you to provide this info. >>>> It's just a regular VirtualFile to the JAR or exploded folder. For the >>>> classpath you could do: >>>> List<VirtualFile> classpath = (VFSDeploymentUnit) unit.getClassPath(); >>>> >>>> Rémy >>>> >>>> _______________________________________________ >>>> jboss-development mailing list >>>> jboss-development(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> -- >> Bill Burke >> JBoss, a division of Red Hat >> http://bill.burkecentral.com >> >> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

On 14 juin 2010, at 16:49, Ales Justin wrote: > > First you get all the classes that are annotated with @Path. > Either they are interfaces or direct classes. > Then you can get super classes of these annotated classes. Bill would need the subclasses and implementations of these annotated types (recursively maybe). _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I also need to ask for classes that extend javax.ws.rs.ext.Application, but that is an entirely different requirement than the @Path one. Ales Justin wrote: > Eh, my bad. > Yeah, it should have said > "Then you get sub classes of these annotated classes". > > /** > * Get sub classes. > * > * @param url the optional classpath entry path > * @param superTypeToLookFor the super type > * @return set of sub types > */ > <T> Set<Class<? extends T>> getSubClassesOf(URL url, Class<T> superTypeToLookFor); > > This is the existing HierarchyIndex api.