Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dtp-dev] New Derby Connection Profile

John,

Sorry about that.  Looks like I was referencing a 1.5JDK in my dev
environment.  I'll have the fix checked in momentarily.

Rob

dtp-dev-bounces@xxxxxxxxxxx wrote on 01/31/2006 10:34:12 AM:

> Rob,
>
> org.eclipse.datatools.connectivity.db.derby doesn't build now, either in
> the automated build on in my dev environment. I'm getting multiple copies
> of the following error:
>
> Severity    Description Resource    In Folder   Location    Creation Time
> 2     The method valueOf(String, int) in the type Integer is not
applicable
> for the arguments (int) DerbyEmbeddedJDBCConnection.java
> org.eclipse.datatools.connectivity.db.
> derby/src/org/eclipse/datatools/connectivity/db/derby
>       line 116    January 31, 2006 12:31:04 PM
>
> Can we get this fixed before the iteration build scheduled for tomorrow?
>
> Thanks,
> John Graham
> Staff Software Engineer
> Sybase, Inc.
>
>
>
>

>              rcernich@sybase.c

>              om

>              Sent by:
To
>              dtp-dev-bounces@e         dtp-dev@xxxxxxxxxxx

>              clipse.org
cc
>

>
Subject
>              01/30/2006 06:52          [dtp-dev] New Derby Connection

>              PM                        Profile

>

>

>              Please respond to

>               DTP development

>                mailing list

>              <dtp-dev@eclipse.

>                    org>

>

>

>
>
>
>
>
> Hey all,
>
> I've implemented a custom connection profile to support embedded Derby
> connections.  This includes a customized connection implementation that
> reuses existing embedded connections and properly disposes of them when
the
> last reference is closed.  I've also moved the driver definition from the
> generic category into a "Derby" category and added a DB2 universal driver
> definition to the generic category.
>
> The new connection profile is keyed to work only with embedded Derby
driver
> definitions.  You should use the DB2 universal driver with the generic DB
> connection profile, since it supports multiple connections and
> java.sql.Connection.close() behaves as expected.  Note, when using the
DB2
> universal driver, you will need to start you Derby DB as a networked
server
> (this is described in detail in the Derby documentation).
>
> Larry, could you do a quick review of the changes to make sure everything
> is copacetic.  Thanks.
>
> Let me know if you have any problems.
> Rob
>
> _______________________________________________
> dtp-dev mailing list
> dtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dtp-dev
>
>
>
> _______________________________________________
> dtp-dev mailing list
> dtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dtp-dev
>



Back to the top