On Thu, May 3, 2012 at 10:17 AM, Anjana Fernando wrote:
> Hi Nuwan,
>
> On Thu, May 3, 2012 at 10:01 AM, Nuwan Bandara wrote:
>
>> Hi Anjana,
>>
>> I would like to know how I can use the data source component for the
>> Database API we provide via Jaggery. right now we using DBCP and obtain a
>>
Hi Nuwan,
On Thu, May 3, 2012 at 10:01 AM, Nuwan Bandara wrote:
> Hi Anjana,
>
> I would like to know how I can use the data source component for the
> Database API we provide via Jaggery. right now we using DBCP and obtain a
> database connection where the user is specifying the connection url
Hi Anjana,
I would like to know how I can use the data source component for the
Database API we provide via Jaggery. right now we using DBCP and obtain a
database connection where the user is specifying the connection url etc. do
you see a usecase to use the data source component.
Regards,
/Nuwan
Hi Amila,
On Thu, May 3, 2012 at 9:28 AM, Amila Jayasekara wrote:
>
> +1 for having a unified data source access management across the
> platform. This will solve the issue of creating multiple database
> pools by each component. But is there a specific reason to switch to
> jdbc-pool from DBCP
On Thu, May 3, 2012 at 8:31 AM, Sumedha Rubasinghe wrote:
> Anjana,
> Good stuff.
> I think we need to inform/discuss moving away from conf/registry.xml &
> conf/user-mgt.xml in architecture list as well. These two files have been
> there for a while, thus an accustomed user community. The databas
