Hi James,
no, I'm trying to use it with Oracle.
However it cannot work with any dialect, because as I described,
it has a bug.
The dialect attribute is set in base class:
ConnectionSourceSkeleton
and the getter in the derived class JNDIConnectionSource
getSQLDialectCode() is returning the attribute from the class
JNDIConnectionSource
where the dialect attribute is initialized with UNKKNOWN and has that value
forever.
To fix, simple comment this code in
/**
* int dialectCode = ConnectionSource.UNKNOWN_DIALECT;
* public int getSQLDialectCode() {
* return dialectCode;
* }
**/
in JNDIConnectionSource
and everything is fine.
Thanks
Arthur Brown
> Are you adding a new Dialect? If yes, then you probably need to
> change at lest a bit of log4j code to know about that new dialect.
>
> --
> James Stauffer
> http://www.geocities.com/stauffer_james/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>>Hi,
>>
>>I have fund a small problem with
>>JNDIConnectionSource.
>>
>>It overwrite the attribute and getter for
>>
>> int dialectCode = ConnectionSource.UNKNOWN_DIALECT;
>> public int getSQLDialectCode() {
>> return dialectCode;
>> }
>>
>>from it's parent class
>>ConnectionSourceSkeleton.
>>
>>However, the function
>>discoverConnnectionProperties()
>>that called to discover the SQL dialect
>>is located in the parent class, where the attribute is set.
>>
>>Evidently, the getter in JNDIConnectionSource is always returning
>>UNKNOWN_DIALECT.
>>
>>Can somebody with write permission correct this please?
>>
>>Thanks
>>Arthur Brown
--
Lassen Sie Ihren Gedanken freien Lauf... z.B. per FreeSMS
GMX bietet bis zu 100 FreeSMS/Monat: http://www.gmx.net/de/go/mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
