Hi Subramanian,
It does not create the destinations in the JMS provider. However admin
objects are the
objects (javax.jms.Queue) that are bound in the appserver's JNDI provider.
If your question is about, why do we need the admin objects specified by RA.
1. In javabean mode of integration, you dont have a destination object
bound in JNDI of
JMS provider.
2. Even in the jndi mode, the app will need to switch the InitialContext
to JMS providers' from
appserver's InitialContext to successfully look up the destination
or queue bound in JMS provider's
JNDI provider.
HTH,
Binod
> Hi I have one clarification
>
> 1. Currently in the JMS integration (for e.g. take OpenJMS I am
> creating the physical destinations (Queue/Topic) through the OpenJMS
> configuration files. In the ra.xml in our generic jms adapter we have
> a provision of specifying adminobjects. Will this also help in
> creating the destinations in the JMS provider? If not what is the use
> of specifying adminobject in the ra.xml?
>
> <adminobject>
> <adminobject-interface>javax.jms.Queue
> </adminobject-interface>
> <adminobject-class>
> com.sun.genericra.outbound.QueueProxy
> </adminobject-class>
> <config-property>
> <config-property-name>
> DestinationJndiName
> </config-property-name>
> <config-property-type>
> java.lang.String
> </config-property-type>
> <config-property-value>
> </config-property-value>
> </config-property>
> <config-property>
> <config-property-name>
> DestinationProperties
> </config-property-name>
> <config-property-type>
> java.lang.String
> </config-property-type>
> <config-property-value>
> </config-property-value>
> </config-property>
> </adminobject>
>
>
>
> ------------------------------------------------------------------------
>
> *Subramanian Easwaran*
> +65 - 6725 6850
> Borland Singapore Pte. Ltd.
>