I went ahead and loosened access as you requested. Though if you update
you should find the need to extend the default factory has been
removed. TorqueClassicDataSource now takes care of assigning a unique
dataSourceName in the event the backend CPDS is set using the
setConnectionPoolDataSource setter.
john mcnally
On Mon, 2002-09-09 at 07:15, Paul Hammant wrote:
> Folks,
>
> <Avalon interloper warning/>
>
> Hi, we are using Torque at work for data pumping. Basically as is it has problems
>with reading
> from Sybase and writing to Oracle (I guess it could be any x to y, and not juse read
>from x and
> write to y).
>
> We have solved the issue by doing a hacky extend of TorqueDataSourceFactory to
>XXXFactory and
> YYYFactory. We reimplemented every method (because of use of private rather than
>protected), but
> basically all we really needed to do was override initialize(conf) and did a
> tcds.setDataSoruceName("XXX") to get it working.
>
> Is there any chance the methods in the TorqueDataSourceFactory could be made
>protected rather than
> private? The same could be true of the scope visibility of
>AbstractDataSourceFactory.
>
> Thanks folks. Great work by the way.
>
> Regards,
>
> - Paul H
>
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
