> 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?
If your question is why is it necessary to have an admin-object element
in RA deployment descriptor, it is an indication to the Java EE
application server of the various administered objects a RA supports and
what is the admin object interface/implementation class etc.
You could refer to 12.4.2.3 Administered Objects of the Connectors 1.5
specification for more information on admin objects.
Thanks
--Siva.
Subramanian Easwaran wrote:
> 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.
>