Hi Donald,
Good question.
>
> When configuring the genericra you deploy the generic RA itself and
> give it details on where the LDAP store is, the base org unit to work
> from, username, password etc. Then you configure the connection
> factory pool and destination objects that result in entries in the app
> server JNDI space. These entries refer to an actual entry in the
> directory server. (eg. cn=QueueConnectionFactory &
> cn=QueueDestination) When using an MDB it seems that the activation
> spec must contain the LDAP lookup values as well. Should it not be
> possible for the directory entries to be specifed in the domain.xml
> rather than in the deployment descriptors for the actual application?
For MDBs, the activation-config-properties are not directly
configured the descriptor. Sun application server do not have a
way to create an inbound-activation-resource. Quite honestly,
there wasnt much demand for such a featire in application server.
Infact, the resource-ref, that facilitates the indirection in case
of outbound connections is used for all kind of resources [eg: jdbc]
and not only resource adapters. That is one reason, why
inbound-activation-resource did not become a priority.
thanks,
Binod.
>
> Many thanks for any thoughts round this area.
>
> Regards
>
>
>
> Donald