continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thierry Lach" <thierry.l...@gmail.com>
Subject Re: JPOX 1.1.7 ?
Date Thu, 15 Mar 2007 16:47:23 GMT
OK, it seems to be something that JBoss is doing to get in the way.  I used
the instructions at
http://docs.codehaus.org/display/CONTINUUM/Database+Configuration (with the
8.1 jdbc jar) and was able to get Continuum up and running using jetty.

On 3/14/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
>
> server 8.2.3-1
> jdbc version: 8.2-504.jdbc3 (and jdbc4)
>
> so I sure hope its not a matter of being that tight :)
>
> I'll monkey around a bit more, right now I am just making sure it
> works with the internal derby
>
> jesse
>
> On 3/14/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > I ran into something similar some time back.  Check to make sure that
> you're
> > using the same version of the postgres jdbc jar as you are the postgres
> > database.  The example on
> > http://docs.codehaus.org/display/CONTINUUM/Database+Configuration uses
> the
> > 8.0 jar.
> >
> > On 3/14/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
> > >
> > > I am getting issues with starting continuum with the jpox 1.1.7 and
> > > postgres myself
> > >
> > > different stacks though
> > >
> > > g: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> > > "PROJECTGROUP_BUILDDEFINITIONS_pkey" for table
> > > "PROJECTGROUP_BUILDDEFINITIONS"
> > > 2007-03-14 12:48:37,539 [main] WARN  General                        -
> > > SQL warning: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit
> > > index "PROJECTNOTIFIER_CONFIGURATION_pkey" for table
> > > "PROJECTNOTIFIER_CONFIGURATION"
> > > 2007-03-14 12:48:37,676 [main] ERROR Schema                         -
> > > An exception was thrown while adding/validating class(es) : ERROR:
> > > function information_schema._pg_keypositions() does not exist
> > > java.sql.SQLException: ERROR: function
> > > information_schema._pg_keypositions() does not exist
> > >         at
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
> > > QueryExecutorImpl.java:1471)
> > >         at org.postgresql.core.v3.QueryExecutorImpl.processResults(
> > > QueryExecutorImpl.java:1256)
> > >         at org.postgresql.core.v3.QueryExecutorImpl.execute(
> > > QueryExecutorImpl.java:175)
> > >         at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(
> > > AbstractJdbc2Statement.java:389)
> > >         at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(
> > > AbstractJdbc2Statement.java:314)
> > >         at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(
> > > AbstractJdbc2Statement.java:221)
> > >         at
> > >
> org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedExportedKeys
> > > (AbstractJdbc2DatabaseMetaData.java:3237)
> > >         at
> > > org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedKeys(
> > > AbstractJdbc2DatabaseMetaData.java:3533)
> > >         at
> org.jpox.store.rdbms.RDBMSStoreHelper.getForeignKeyInfoForTable
> > > (RDBMSStoreHelper.java:376)
> > >         at org.jpox.store.rdbms.table.TableImpl.getExistingForeignKeys
> (
> > > TableImpl.java:937)
> > >         at org.jpox.store.rdbms.table.TableImpl.validateForeignKeys(
> > > TableImpl.java:421)
> > >         at org.jpox.store.rdbms.table.TableImpl.validateConstraints(
> > > TableImpl.java:394)
> > >         at org.jpox.store.rdbms.table.ClassTable.validateConstraints(
> > > ClassTable.java:2875)
> > >         at
> > > org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(
> > > RDBMSManager.java:3110)
> > >
> > > On 3/14/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > > > Yeah, that was my thought also.
> > > >
> > > > On 3/14/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
> > > > >
> > > > > have you tried it with postgres outside of jboss?  I want to
> narrow
> > > > > down the factors here
> > > > >
> > > > >
> > > > >
> > > > > On 3/14/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > > > > > That's right. I knew that patch for transaction levels didn't
> solve
> > > it
> > > > > on
> > > > > > its own, so my hopes got up with the mention of JPOX 1.1.7 and
> > > postgres
> > > > > last
> > > > > > week.
> > > > > >
> > > > > > On 3/13/07, Jesse McConnell <jesse.mcconnell@gmail.com>
wrote:
> > > > > > >
> > > > > > > I set the transaction lvls to READ_COMMITTED as well, so
that
> > > didn't
> > > > > > > fix you either huh?
> > > > > > >
> > > > > > > hrm
> > > > > > >
> > > > > > > On 3/13/07, Thierry Lach <thierry.lach@gmail.com>
wrote:
> > > > > > > > JPOX 1.1.7 doesn't correct the problems with Postgres.
 I've
> > > added
> > > > > an
> > > > > > > > updated stack trace to
> > > > > http://jira.codehaus.org/browse/CONTINUUM-1181
> > > > > > > >
> > > > > > > > On 3/13/07, Jesse McConnell <jesse.mcconnell@gmail.com>
> wrote:
> > > > > > > > >
> > > > > > > > > yes, and I setup the bundled for m2 and got them
into
> place
> > > about
> > > > > an
> > > > > > > > > hour ago...will be synced into the main repos
sometime
> soon
> > > > > > > > >
> > > > > > > > > jesse
> > > > > > > > >
> > > > > > > > > On 3/13/07, Thierry Lach <thierry.lach@gmail.com>
wrote:
> > > > > > > > > > Did JPOX 1.1.7 get released yesterday?
> > > > > > > > > >
> > > > > > > > > > On 3/7/07, Erik Bengtson <erik@jpox.org>
wrote:
> > > > > > > > > > >
> > > > > > > > > > > FYI, JPOX 1.1.7 will be released next
monday. It fixes
> the
> > > > > issue
> > > > > > > with
> > > > > > > > > > > postgres.
> > > > > > > > > > >
> > > > > > > > > > > You can try it out, if you like, before
we release.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > >
> > > http://www.jpox.org/downloads/maven/jpox/jars/jpox-1.1-SNAPSHOT.jar
> > > > > > > > > > >
> > > > > > > > > > > Regards
> > > > > > > > > > >
> > > > > > > > > > > Quoting Jesse McConnell <jesse.mcconnell@gmail.com>:
> > > > > > > > > > >
> > > > > > > > > > > > Ok, well the little poll thread
I made seemed to be
> > > strongly
> > > > > in
> > > > > > > > > favor
> > > > > > > > > > > > of getting things pulled together
to start getting
> alpha
> > > > > > > releases
> > > > > > > > > out
> > > > > > > > > > > > of continuum.  So with that in
mind here is a list
> of a
> > > few
> > > > > > > things
> > > > > > > > > > > > that we need to get in order for
an alpha release
> that I
> > > > > > > shamelessly
> > > > > > > > > > > > started base on bretts comments
> > > > > > > > > > > >
> > > > > > > > > > > > - properly mark up the model as
it was for 1.0.3release
> > > > > > > > > > > > - add methods to continuum-data-management
to
> utilise
> > > that
> > > > > and
> > > > > > > then
> > > > > > > > > > > > make any necessary transformations
(c-d-m will do
> the
> > > basic
> > > > > > > 1-to-1
> > > > > > > > > > > > conversions)
> > > > > > > > > > > > - probably write a little CLI
to fire it off.
> > > > > > > > > > > > - vet jira for a 1.1 alpha 1 release
version and
> maybe
> > > > > schedule
> > > > > > > out
> > > > > > > > > a
> > > > > > > > > > > > couple of alpha-# releases.
> > > > > > > > > > > >
> > > > > > > > > > > > I think I'll start in on the data
management bit now
> > > since
> > > > > that
> > > > > > > > > seems
> > > > > > > > > > > > like the biggest hurdle.  I am
not convinced we
> really
> > > need
> > > > > to
> > > > > > > worry
> > > > > > > > > > > > about a continuum 1.0.3 ->
continuum 1.1 migration
> > > > > ability...its
> > > > > > > not
> > > > > > > > > a
> > > > > > > > > > > > difficult thing to get projects
loaded back up into
> > > > > > > continuum...but
> > > > > > > > > > > > we'll see I guess.
> > > > > > > > > > > >
> > > > > > > > > > > > anyone have anything to add?
> > > > > > > > > > > >
> > > > > > > > > > > > jesse
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > jesse mcconnell
> > > > > > > > > > > > jesse.mcconnell@gmail.com
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > jesse mcconnell
> > > > > > > > > jesse.mcconnell@gmail.com
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > jesse mcconnell
> > > > > > > jesse.mcconnell@gmail.com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > jesse mcconnell
> > > > > jesse.mcconnell@gmail.com
> > > > >
> > > >
> > >
> > >
> > > --
> > > jesse mcconnell
> > > jesse.mcconnell@gmail.com
> > >
> >
>
>
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message