-
15. Re: JSR77 View
"scott.stark@jboss.org" wrote:
By just generating the names off of the deployment names, and metadata. It does not need to match or be derived from any mbeans that may be generated by the deployers. There are 3 parts to the jsr77 namespace:
- hierarchy - that should be known from the deployment + the top level domain
- module type - known from the metadata
- component type - known from the metadata
I've committed this part.
And it surprisingly works. :-)
See AbstractJSR277Deployer for the missing TODOs,
extracting root and components mbeans / ObjectNames. -
-
17. Re: JSR77 View
"scott.stark@jboss.org" wrote:
and I see you updated JSR77SpecUnitTestCase, great.
It's not yet fully enabled.
The component parts - servlets, ejbs, ... - are still disabled.
If we can somehow extract info within those 2 TODOs in AbstractJSR277Deployer,
everything should fall in place.
You mentioned managed view.
Then I guess we would need to add new @JSR77Name annotation to jboss-man? -
18. Re: JSR77 View
I'll take a look at the todos later today.
I'm not sure if we need a new annotation or just a new property on ManagementObject or ManagedDeployment, ManagementComponent. The ManagedDeployment/ManagedComponent + the higher level hierarchy of the jsr77 namespace is what best matches the jsr77 module/component conventions.