I ran into a similar problem using JBoss as the managed environment.  Could
we add that to the list for 1.0.2?  The method names needed are below:

    protected static final String UNWRAP_CONN_METHOD_NAMES[] =
            {
                "unwrapCompletely"      /* Oracle 10g */,
                "getInnermostDelegate"  /* Commons DBCP */,
                "getVendorConnection"   /* BEA WebLogic */,
                "getJDBC"               /* P6Spy */
                "getUnderlyingConnection" /* JBoss */
            };

and

    protected static final String UNWRAP_PS_METHOD_NAMES[] =
            {
                "getInnermostDelegate"  /* Commons DBCP */,
                "getJDBC"               /* P6Spy */
                "getUnderlyingStatement" /* JBoss */
            };

That should do the trick.

Don Lyon
dairy.com

-----Original Message-----
From: Martin Kal�n [mailto:[EMAIL PROTECTED]
Sent: Monday, March 14, 2005 11:57 PM
To: OJB Users List
Subject: Re: Oracle Driver jdbc10.1.0.2


Dougall Squair wrote:
> Are you running within a managed environment? We seem to be getting a
> similar exception 
> when we use the Oracle9i platform support class, I suspect it's caused by
> WebLogic wrapping the Oracle connection object.

Generic unwrapping of both Connection and PreparedStatement have been 
added to the PlatformOracle9iImpl. Current implementation knows about 
Oracle10g, BEA WebLogic, Apache Commons DBCP and P6spy wrappers.

The PlatformWLOracle9iImpl has been marked as deprecated, as the 
standard platform should work also in BEA WebLogic.

If unwrapping fails, the 9i platform is still usable (but has the 2k/4k 
BLOB/CLOB limits and no ORA performance-extensions activated).

This is in CVS now and should be available with the upcoming OJB 1.0.2 
release.

Please re-test if possible.

Regards,
  Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----------------------------------
The information contained in this e-mail message is intended only for the
personal and confidential use of the recipient(s) named above. If the reader
of this message is not the intended recipient or an agent responsible for
delivering it to the intended recipient, you are hereby notified that you
have received this communication in error and that any review,
dissemination, distribution, or copying of this message is strictly
prohibited. If you have received this communication in error, please notify
us immediately by e-mail, and delete the original message.

Reply via email to