I wanted to change the config for the @JMX aspect, but currently this configis defined in the aop project, so it would need a new release of aop to change it????I've moved it to the aspects project in the appserver codebase.

The first problem is because the POJO names are the same as the JMX names.

With the new ServiceController implementation, the JMX objects are real contextsin the MC that you can depend upon. i.e. they go through the ServiceControllerlifecycle.

I don't understand the second test.It says jboss.aop:name=BeanWithDependency should not have been found?

The only difference between the old and the new JMX lifecycle is theservice controller lifecycle is now invoked for the MBean.But this test is NOT looking at the lifecycle it is just looking for the registered MBean,there has been no change to this.

The only difference between the old and the new JMX lifecycle is theservice controller lifecycle is now invoked for the MBean.But this test is NOT looking at the lifecycle it is just looking for the registered MBean,there has been no change to this.