[wildfly-dev] JAR scanning
tsegismo at redhat.com
Tue Sep 23 06:06:03 EDT 2014
Our CLI Alert Sender is not part of the RHQ extension. It's a plugin
loaded by the RHQ EAR (so to speak). So yes, runtime only.
Le 23/09/2014 11:47, Tomaž Cerar a écrit :
> 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.
> On Tue, Sep 23, 2014 at 9:32 AM, Thomas Segismont <tsegismo at redhat.com
> <mailto:tsegismo at redhat.com>> wrote:
> 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:
> VirtualFile virtualFile = (VirtualFile)
> // 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!
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org <mailto:wildfly-dev at lists.jboss.org>
More information about the wildfly-dev