[jboss-dev] missing security config file?

[Ales Justin]

This is cause by:
  - 
http://fisheye.jboss.org/browse/JBossAS/projects/jboss-deployers/trunk/deployers-vfs/src/main/org/jboss/deployers/vfs/deployer/kernel/BeanMetaDataDeployer.java?r1=75281&r2=76637
  - https://jira.jboss.org/jira/browse/JBDEPLOY-69

It messes up the Scopes + MetaDataRetrievals.
So the Pojo IoC annotations are not found.
In this case it's the @Create, @Start, ... on ServiceSupportMBean.

I ported the security example here:
  - 
http://anonsvn.jboss.org/repos/jbossas/projects/demos/trunk/models/src/main/org/jboss/demos/models/

It was failing with the JBDEPLOY-69.
This annotated bean also had problems, not finding the marked constructor:
  - 
http://anonsvn.jboss.org/repos/jbossas/projects/demos/trunk/models/src/main/org/jboss/demos/models/guice/PojoModule.java
Removing JBDEPLOY-69 patch, made things work again.

So, JBDEPLOY-69 is now re-opened.
Expecting better tests. :-)

Stefan Guilhen wrote:
> Both SecurityConfig and XMLLoginConfig were old mbeans that have been 
> configured as mc beans while still inheriting ServiceMBeanSupport (so 
> that they could be configured both as mbeans and as mc beans).
> 
> I've removed the ServiceMBeanSupport inheritance from the beans and 
> removed the ServiceMBean inheritance from their interfaces as well and 
> now both beans start correctly (also had to add start and stop methods 
> to replace startService and stopService). So now those beans can only be 
> configured as mc beans and use the @JMX annotation to export their 
> "MBean view".
> 
> My question is whether inheriting ServiceMBeanSupport is now considered 
> wrong for a mc bean or not. If it is, and beans are only supposed to be 
> configured as mc beans, then I'll commit the changes I've made to be in 
> line with Ales/Adrian's changes.