Yes, search the forum or read through the quick start guide.
come on, almost every other question on this forum is about how to use the RMI connector...
Heh, ok, I though the mention of "sparse docs" would answer your first reply and the reference I gave in the old docs would clearly state it's not RMI. I'll be more clear.
In 2.4.4 I did this via http and can't find it's equal in 3.0.1 and every reply I get sort of dodges the yes or no it works and if so, some hint on how. If http does work, that's ideal as I'd like to communicate to the mbeans across tcp/ip domains. If not, I'll have to find the RMI way and leave the feature that relies on http out of my stuff till it does come around.
Sorry if I sound like I'm losing it, but I almost am at a few weeks of firing off posts at different angles and dozens of replies with nothing really to say.
Thanks for taking the time.
You can do it from any web client
This creates a queue called "blah" bound at
"queue/blah" within jndi.
You probably want to configure some security for this.
Big thnxs, that's what I had been trying to construct ... and it's back to working like normal.
So now that I had about 3/4 of the way learned and implemented an MBean (still not working, but close I'm sure), ...
Are there any big advantages of using an RMI Adaptor over an HTML adaptor?
I did http because I've got a few solutions that have agents over separate domains and needed a way to get through the firewalls.
Thanks again, exactly what I was looking for.
AFAIR, the current RMI adaptor uses anon ports so that's going to be problem for any firewall setup (I'm not looking at the code so could remember wrong tho), so you need to tweak the code abit to allow a config of specific port for exporting the remote object for firewalls (and you still need to punch a hole for that port).
There's some mechanism in RMI to tunnel thru HTTP but I haven't looked into that.
Also, you could just use a simple SOAP connector (download an example from my book sources that uses GLUE), thats pure HTTP. The advantage of connectors such as RMI or SOAP is you get the MBeanServer API on the client side (which is alot more stable than relying on the HTTP requests of a specific HTML adaptor).