ObjectName
From Resin 3.0
(Difference between revisions)
| Line 20: | Line 20: | ||
resin:type=class-name,name=identifier[,context] | resin:type=class-name,name=identifier[,context] | ||
| − | For example, the unique [ServerMXBean] in a Resin instance has the name: | + | For example, the unique [[ServerMXBean]] in a Resin instance has the name: |
resin:type=ServerMXBean | resin:type=ServerMXBean | ||
| Line 28: | Line 28: | ||
resin:type=ClusterMXBean,name=app-tier | resin:type=ClusterMXBean,name=app-tier | ||
| − | And a [web-app] with an id='/foo' in the virtual host 'www.foo.com' would have the name: | + | And a [[web-app]] with an id='/foo' in the virtual host 'www.foo.com' would have the name: |
resin:type=WebAppMXBean,name=/foo,Host=www.foo.com | resin:type=WebAppMXBean,name=/foo,Host=www.foo.com | ||
Revision as of 03:39, 4 August 2006
The [JMX] ObjectName describes the name of a managed object.
resin:type=WebApp,name=/foo,host=wiki.caucho.com
The ObjectName has two main sections:
- A naming domain (e.g. "resin:")
- An association list of key,value properties
domain
The domain is used as a namespace to distinguish naming conventions. So "resin" uses the Resin naming conventions. "j2ee" uses J2EE naming conventions.
Resin conventions
Each objects managed by Resin have the following convention:
resin:type=class-name,name=identifier[,context]
For example, the unique ServerMXBean in a Resin instance has the name:
resin:type=ServerMXBean
A [cluster] with an id="app-tier" would have the name:
resin:type=ClusterMXBean,name=app-tier
And a web-app with an id='/foo' in the virtual host 'www.foo.com' would have the name:
resin:type=WebAppMXBean,name=/foo,Host=www.foo.com
Contexts
Currently, Resin has two contexts, Host and WebApp.
