Re: [wildfly-dev] JAR scanning
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>
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
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Attachments:
- attachment.html (text/html — 2.0 KB)