Max Poon wrote:
> Hello everybody
> Cross-posted for any advice.
>
Hmm -
Well i thought that the level of the RA it is acting as defaults
since if i use it in the MDB (activation-spec) for sun-ejb.jar i need to
put back all those i.
As for the connection pool too i suppose you can also change them as
this override the RA value
Unless it see that this is not like that or i misunderstood your question...
> Thanks.
>
> ------------------------------------------------------------------------
>
> Subject:
> EIS-specific properties defined at RA level for GenericJMSRA ?
> From:
> Max Poon <maxpoon_at_gmail.com>
> Date:
> Fri, 13 Jan 2006 11:52:30 +0800
> To:
> Binod <Binod.Pg_at_Sun.COM>
>
> To:
> Binod <Binod.Pg_at_Sun.COM>
> CC:
> users_at_genericjmsra.dev.java.net
>
>
> Hi Binod
>
> I noticed from article Getting Started with Connectors in Sun Java
> System Application Server Platform Edition 8.0
> <http://developers.sun.com/prodtech/appserver/reference/techart/as8_connectors/>
> that we can "create multiple connector connection pools for a
> connection definition in a functional resource adapter instance".
>
> However, in the GenericJMSRA User Guide
> <https://genericjmsra.dev.java.net/docs/userguide/userguide.html>
> "Resource Adapter Properties", I discovered that parameters like
>
> * ProviderIntegrationMode
> * ConnectionFactoryClassName
> * QueueConnectionFactoryClassName
> * ...
> * JndiProperties
> * CommonSetterMethodName
> * UserName
> * Password
>
> which are specific to each of the different EIS (i.e.
> QueueConnectionFactoryClassName=com.ibm.mq.jms.MQQueueConnectionFactory)
> are defined in the generic resource adapter level, instead of
> Connection Pool level. In this case, how can different connection /
> connection-pool for different EIS (e.g. WMQ, TibEMS) be sharing one
> and the same genericjmsra definition?
>
> Thanks for any advice.
>
> Max