Improvements to the DataSource Connection Pool
----------------------------------------------
Key: SYNAPSE-416
URL: https://issues.apache.org/jira/browse/SYNAPSE-416
Project: Synapse
Issue Type: Improvement
Components: Core
Affects Versions: NIGHTLY
Reporter: indika priyantha kumara
Assignee: indika priyantha kumara
Fix For: FUTURE
Improvements to the DataSource Connection Pool
1) If the DB connection pool is defined in the synapse.properties, then , those
need to be accessed just providing data source name. Simply, we have to
differentiates the accusing datasources that we have created and datasources
that we are looking up.
Then , For access datasources we have defined (Example dblookup
mediator)
<pool>
<dsName>lookupds</dsName>
</pool>
and for any external datasources as before
<pool>
<dsName>lookupds</dsName>
<icClass>com.sun.jndi.rmi.registry.RegistryContextFactory</icClass>
<url>rmi://localhost:2199</url>
<user>esb</user>
<password>esb</password>
</pool>
11) If the datasources that we have defined is not intended to use by
any other application. Then, we never want to register those in the JNDI
tree. Those can be in a local pool. Currently, all are registered in the JNDI.
This need to be configurable so that if someone want to avoid JNDI
registration , he can tell it by configuration option.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
