Jason:
You could have a look at the way it is implemented in the CLI to see how
the MBeanServer calls are made. Have a look at JMSDestination,
MQJMXConnectorInfo and MQAddressList classes to see how this is being
done. You should be able to reuse some of these classes as well.
Let me know if you have any further questions or need to talk.
Thx,
Satish
Jason Lee wrote:
> I'm trying to finish up the port of the JMS support in the Admin
> Console from v2 to v3. The only major functionality left is the
> physical destination management, which is done via JMX directly
> against the broker. Anyone familiar with how that code worked in v2
> or how it should be in v3 have time to give me a nudge in the right
> direction? For instance, if I can get a connection to the MBeanServer
> for the broker, I can probably take it from there, but getting the
> connection the v2 doesn't appear to be working anymore. Additionally,
> is the MQ instance started with the server, or must it be started
> manually?
>
> Many thanks! :)
>
> <http://www.java.com> * Jason Lee *
> Senior Java Developer
> GlassFish Administration Console
>
> *Sun Microsystems, Inc.*
> Phone x31197/+1 405-343-1964
> Email jasondlee_at_sun.com <mailto:jasondlee_at_sun.com>
> Blog http://blogs.sun.com/jasondlee
> Blog http://blogs.steeplesoft.com
>
>