Jesper Pedersen [
http://community.jboss.org/people/jesper.pedersen] created the
discussion
"Re: IronJacamar RHQ plugin development"
To view the discussion, visit:
http://community.jboss.org/message/590966#590966
--------------------------------------------------------------
I think you misunderstood me.
The network transport part is specific to IronJacamar - our own protocol - to retrieve
information or invoke operations. There is no serialization of the ManagementRepository
going on - nor proxy stuff.
The packages you mentions are correct - they contains the functionality needed to discover
the environment, like the embedded container.
F.ex. the "as7" and "standalone" will have a discovery implementation
for accessing remote containers based on the "manual add" functionality (
http://pilhuhn.blogspot.com/search?q=manualadd
http://pilhuhn.blogspot.com/search?q=manualadd).
The focus should be on the core and embedded packages first, as we need that for testing
the plugin, and defining which functionality we need from the IronJacamar container. Once
that is done we will do an as7.InVMDiscovery class for AS 7 specific discovery. After that
an as7.RemoteDiscovery class.
The "standalone" package has the lowest priority as the standalone distribution
doesn't feature a RHQ platform at the moment. It is correct that a bridge between the
plugin and JMX would be the quickest solution.
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/590966#590966]
Start a new discussion in IronJacamar Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]