tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stevo Slavić <ssla...@gmail.com>
Subject Re: Multiple persistence units, multiple data sources
Date Wed, 27 Jun 2012 17:22:07 GMT
Configuring

<property name="openjpa.jdbc.Schema" value="PUBLIC"/>

in persistence.xml did the trick.

Maybe https://issues.apache.org/jira/browse/OPENJPA-1812 is related ticket.

Romain and David, thanks for support!

Kind regards,
Stevo Slavić.

On Wed, Jun 27, 2012 at 7:07 PM, Stevo Slavić <sslavic@gmail.com> wrote:

> One of the entities maps to table "parameters".
> When I enabled trace log level for openjpa I was surprised to see:
>
> ...
> 17:35:29.845 [Thread-2] TRACE openjpa.jdbc.Schema - Reading table
> information for schema name "null", table name "PARAMETERS".
> 17:35:29.845 [Thread-2] TRACE openjpa.jdbc.JDBC - <t 311600862, conn
> 710612217> getColumns: PUBLIC, null, PARAMETERS, null
> 17:35:29.890 [Thread-2] TRACE openjpa.jdbc.Schema - Reading column
> information for table "INFORMATION_SCHEMA.PARAMETERS".
> 17:35:29.890 [Thread-2] TRACE openjpa.jdbc.Schema - Found existing column
> "SPECIFIC_CATALOG" on table "INFORMATION_SCHEMA.PARAMETERS".
> ...
>
>
> OpenJPA for the purpose of building schema is querying HSQLDBs internal
> INFORMATION_SCHEMA schema and it tries to add ID column (found on entity
> but not in HSQLDBs INFORMATION_SCHEMA.PARAMETERS table) to PARAMETERS table
> in that schema, but that schema is HSQLDBs system schema and is (luckly)
> read-only, resulting in failure.
> http://hsqldb.org/doc/2.0/guide/databaseobjects-chapt.html#dbc_overview
>
> Shouldn't OpenJPA be using PUBLIC schema instead? I guess this is a bug in
> OpenJPA.
>
> Have to check if there is a switch/configuration option to force OpenJPA
> to use "PUBLIC" schema.
>
> Kind regards,
> Stevo Slavić.
>
>
>
> On Wed, Jun 27, 2012 at 6:55 PM, David Blevins <david.blevins@gmail.com>wrote:
>
>>
>> On Jun 27, 2012, at 3:46 AM, Stevo Slavić wrote:
>>
>> > Then I
>> > upgraded openejb too, from 3.1.4 to 4.0.0 but not all tests are passing.
>> > To be more specific there is 1 passing, and 2 failing tests, all in same
>> > module using shared jndi.properties, persistence.xml, and ejb-jar.xml
>> > In jndi.properties (see [1]) two data sources are configured for
>> openejb to
>> > create.
>>
>> Did you by chance also change from using the `new IntialContext` approach
>> in the test case to using the new `EJBContainer.createEJBContainer`
>> approach?
>>
>> (not bad, we just need adjust the test setup)
>>
>>
>> -David
>>
>>
>

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