Hi everyone, In RHQ I need a way to list my domain classes at runtime (when preparing the CLI environment for execution, but that's another story). In the past, for the same issue with another project, I did something like looking for the persistence.xml file in the classpath and then scan the JAR where it is found. I wonder if there's something I could re-use from our EAP6.3-alpha base. Any idea? Thanks, Thomas _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

URI uri = getURI("/test.rar"); final VirtualFile virtualFile = VFS.getChild(uri); final Indexer indexer = new Indexer(); final List<VirtualFile> classChildren = virtualFile.getChildren(new SuffixMatchFilter(".class", VisitorAttributes.RECURSE_LEAVES_ONLY)); for (VirtualFile classFile : classChildren) { InputStream inputStream = null; try { inputStream = classFile.openStream(); indexer.index(inputStream); } finally { VFSUtils.safeClose(inputStream); } } On Sep 22, 2014, at 11:53 AM, Jason Greene <jason.greene(a)redhat.com&gt; wrote: > You can do a similar technique. Load a file in your deployment via getResource on a clasloader. Then you will get a VFS uri. If you convert it to a URL and call openContent on it you will get a VFS VirtualFile, and then using that you can browse anything int he deployment. > > > On Sep 22, 2014, at 9:29 AM, Thomas Segismont <tsegismo(a)redhat.com&gt; wrote: > >> Hi everyone, >> >> In RHQ I need a way to list my domain classes at runtime (when preparing >> the CLI environment for execution, but that's another story). >> >> In the past, for the same issue with another project, I did something >> like looking for the persistence.xml file in the classpath and then scan >> the JAR where it is found. >> >> I wonder if there's something I could re-use from our EAP6.3-alpha base. >> Any idea? >> >> Thanks, >> Thomas >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > -- > Jason T. Greene > WildFly Lead / JBoss EAP Platform Architect > JBoss, a division of Red Hat > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev

My index is correctly built and now I'm trying to find how I can read org.jboss.jandex.ClassInfo#flags to determine if the class is public.

Just for record if that is not sure. If this is deployment properly deployed in WildFly jandex index for it is automatically build for it during deploy time. If your code is in Extension(subsystem) it can register DeploymentUnitProcessor which can access this indexes during deployment. Otherwise if your code is run time only then what you are doing is the right way. -- tomaz On Tue, Sep 23, 2014 at 9:32 AM, Thomas Segismont <tsegismo(a)redhat.com <mailto:tsegismo@redhat.com>> wrote: Hi, Le 22/09/2014 17:23, Jason Greene a écrit : > Yeah something like that. Although I just want to stress the importance of using the ClassLoader for the deployment, as due to a historical oversight the path is different between windows and unix. Understood. For the record: getClass().getClassLoader().getResources("META-INF/persistence.xml"); Then: VirtualFile virtualFile = (VirtualFile) url.openConnection().getContent(); // up to the archive root virtualFile = virtualFile.getParent().getParent(); My index is correctly built and now I'm trying to find how I can read org.jboss.jandex.ClassInfo#flags to determine if the class is public. Thank you both for indications and the code snippet! Regards, Thomas _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/wildfly-dev