-
1. Re: Annotating KernelDeployment with management info
The Boolean isScoped method of KernelDeployment needs to be changed to getScoped due to the previously discussed issue of Boolean isX not being the getter for Boolean property x.
-
2. Re: Annotating KernelDeployment with management info
I'll have a look at it, perhaps it can be changed to plain boolean. Can't remember the reason now why I put it to full Boolean. ;-)
-
-
4. Re: Annotating KernelDeployment with management info
I checked in just enough changes to allow the default AbstractManagedObjectFactory to build a ManagedObject set for a KernelDeployment.
In reality the BeanDeployer should be implementing the ManagedObjectCreator.build method as the deployer has the metadata and understands things like annotation overrides. Its not clear to me that the BeanInfo beanInfo = configuration.getBeanInfo(clazz) call used by the AbstractManagedObjectFactory is going to have the beans.xml annotations/overrides applied. Would it? -
5. Re: Annotating KernelDeployment with management info
"scott.stark@jboss.org" wrote:
I checked in just enough changes to allow the default AbstractManagedObjectFactory to build a ManagedObject set for a KernelDeployment.
In reality the BeanDeployer should be implementing the ManagedObjectCreator.build method as the deployer has the metadata and understands things like annotation overrides. Its not clear to me that the BeanInfo beanInfo = configuration.getBeanInfo(clazz) call used by the AbstractManagedObjectFactory is going to have the beans.xml annotations/overrides applied. Would it?
No. -
6. Re: Annotating KernelDeployment with management info
The overrides only come after the bean's classloader is resolved - which is in PreInstall state.
See KernelScopeInfo.addMetaData, which gets invoked withKernelMetaDataRepository repository = controller.getKernel().getMetaDataRepository(); repository.addMetaData(context);
in PreInstallAction class.
That's where annotations from xml get into metadata repo.