DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36137>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36137 Summary: Slide fails when using Oracle and WebLogic with J2EE Store (OracleRDBMSAdapter) Product: Slide Version: 2.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: Stores AssignedTo: slide-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] WebLogic in its wisdom wraps BLOBS from Oracle when accessing Oracle via DataSources. OracleRDBMSAdapter hard codes in the Blob class "oracle.sql.BLOB" but when accessing Blobs via a WebLogic DataSource, this needs to be "weblogic.jdbc.vendor.oracle.OracleThinBlob". To work around this we just extended OracleRDBMSAdapter to create an OracleWebLogicRDBMSAdapter which overrode the Constructor and set the above class as the classname in the Class.forName() method. A slightly better solution would be to allow the blob class to be fed in as a parameter in Domain.xml. This would require setParameters() to be overriden in OracleRDBMSAdapter. The default class could be set in the constructor and the call to Class.forName could be delayed until the setParameters() call. If no suitable "blobClass" parameter was set, it would default to the current code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
