You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Web developer <we...@gmail.com> on 2010/05/17 12:54:45 UTC
Test run
Got the following notice when trying to run tests:
enhance.all.entities:
[echo] running enhancer
160 WARN [main] openjpa.Runtime - The configuration property named
"openjpa.loglevel" was not recognized and will be ignored, although the name
closely matches a valid property called "openjpa.Log".
Logging not configured properly? John
Re: Test run
Posted by Web developer <we...@gmail.com>.
I can get sources of needed version from trunk. Not kind if big deal. I will
do as you recommend. John
2010/5/17 Michael Dick <mi...@gmail.com>
> Hi John,
>
> 2.0.0-beta3 predates the changes which fix this issue. The message is
> benign
> and can safely be ignored. You could merge the changes for revision
> 923929<http://svn.apache.org/viewcvs?view=rev&rev=923929> back
> to your copy of the source if you want - that should fix the problem.
>
> Regards,
> -mike
>
> On Mon, May 17, 2010 at 9:54 AM, Web developer <webautomator2@gmail.com
> >wrote:
>
> > My version is 2.0.0. Extracted from
> apache-openjpa-2.0.0-beta3-binary.zip.
> > Thanks! John
> >
> > 2010/5/17 Michael Dick <mi...@gmail.com>
> >
> > > Hi
> > >
> > > Which version of OpenJPA are you building? Last month (IIRC) we removed
> > the
> > > openjpa.loglevel property from the builds (1.2.x - trunk). If you have
> an
> > > older version of one of the pom.xml files it might still show up
> though.
> > >
> > > FWIW the changes were done under
> > > OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557>
> > > .
> > >
> > > -mike
> > >
> > > On Mon, May 17, 2010 at 5:54 AM, Web developer <
> webautomator2@gmail.com
> > > >wrote:
> > >
> > > > Got the following notice when trying to run tests:
> > > >
> > > > enhance.all.entities:
> > > > [echo] running enhancer
> > > > 160 WARN [main] openjpa.Runtime - The configuration property named
> > > > "openjpa.loglevel" was not recognized and will be ignored, although
> the
> > > > name
> > > > closely matches a valid property called "openjpa.Log".
> > > >
> > > > Logging not configured properly? John
> > > >
> > >
> >
>
Re: Test run
Posted by Rick Curtis <cu...@gmail.com>.
Cross posting to the users mailing list....
Please turn on SQL trace to see what is being generated.
-Dopenjpa.Log=SQL=trace or <property name="openjpa.Log" value="SQL=trace" />
Thanks,
Rick
On Wed, May 19, 2010 at 8:04 AM, Web developer <we...@gmail.com>wrote:
> But what I can't ignore is that bug with log4j config that I posted
> earlier.
> Especially with a sequence generator. It says that the table is created in
> HSQLDB database. But manual investigation shows no such table. But when
> generator is forced to re-create the (theoretically) existing sequence
> related table - it says that table is existing(?!). So I need help with
> that
> log4j bug to figure out what is happening. Looks like that it is sequence
> generator related bug. John
>
>
Re: Test run
Posted by Web developer <we...@gmail.com>.
But what I can't ignore is that bug with log4j config that I posted earlier.
Especially with a sequence generator. It says that the table is created in
HSQLDB database. But manual investigation shows no such table. But when
generator is forced to re-create the (theoretically) existing sequence
related table - it says that table is existing(?!). So I need help with that
log4j bug to figure out what is happening. Looks like that it is sequence
generator related bug. John
2010/5/17 Michael Dick <mi...@gmail.com>
> Hi John,
>
> 2.0.0-beta3 predates the changes which fix this issue. The message is
> benign
> and can safely be ignored. You could merge the changes for revision
> 923929<http://svn.apache.org/viewcvs?view=rev&rev=923929> back
> to your copy of the source if you want - that should fix the problem.
>
> Regards,
> -mike
>
> On Mon, May 17, 2010 at 9:54 AM, Web developer <webautomator2@gmail.com
> >wrote:
>
> > My version is 2.0.0. Extracted from
> apache-openjpa-2.0.0-beta3-binary.zip.
> > Thanks! John
> >
> > 2010/5/17 Michael Dick <mi...@gmail.com>
> >
> > > Hi
> > >
> > > Which version of OpenJPA are you building? Last month (IIRC) we removed
> > the
> > > openjpa.loglevel property from the builds (1.2.x - trunk). If you have
> an
> > > older version of one of the pom.xml files it might still show up
> though.
> > >
> > > FWIW the changes were done under
> > > OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557>
> > > .
> > >
> > > -mike
> > >
> > > On Mon, May 17, 2010 at 5:54 AM, Web developer <
> webautomator2@gmail.com
> > > >wrote:
> > >
> > > > Got the following notice when trying to run tests:
> > > >
> > > > enhance.all.entities:
> > > > [echo] running enhancer
> > > > 160 WARN [main] openjpa.Runtime - The configuration property named
> > > > "openjpa.loglevel" was not recognized and will be ignored, although
> the
> > > > name
> > > > closely matches a valid property called "openjpa.Log".
> > > >
> > > > Logging not configured properly? John
> > > >
> > >
> >
>
Re: Test run
Posted by Michael Dick <mi...@gmail.com>.
Hi John,
2.0.0-beta3 predates the changes which fix this issue. The message is benign
and can safely be ignored. You could merge the changes for revision
923929<http://svn.apache.org/viewcvs?view=rev&rev=923929> back
to your copy of the source if you want - that should fix the problem.
Regards,
-mike
On Mon, May 17, 2010 at 9:54 AM, Web developer <we...@gmail.com>wrote:
> My version is 2.0.0. Extracted from apache-openjpa-2.0.0-beta3-binary.zip.
> Thanks! John
>
> 2010/5/17 Michael Dick <mi...@gmail.com>
>
> > Hi
> >
> > Which version of OpenJPA are you building? Last month (IIRC) we removed
> the
> > openjpa.loglevel property from the builds (1.2.x - trunk). If you have an
> > older version of one of the pom.xml files it might still show up though.
> >
> > FWIW the changes were done under
> > OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557>
> > .
> >
> > -mike
> >
> > On Mon, May 17, 2010 at 5:54 AM, Web developer <webautomator2@gmail.com
> > >wrote:
> >
> > > Got the following notice when trying to run tests:
> > >
> > > enhance.all.entities:
> > > [echo] running enhancer
> > > 160 WARN [main] openjpa.Runtime - The configuration property named
> > > "openjpa.loglevel" was not recognized and will be ignored, although the
> > > name
> > > closely matches a valid property called "openjpa.Log".
> > >
> > > Logging not configured properly? John
> > >
> >
>
Re: Test run
Posted by Web developer <we...@gmail.com>.
My version is 2.0.0. Extracted from apache-openjpa-2.0.0-beta3-binary.zip.
Thanks! John
2010/5/17 Michael Dick <mi...@gmail.com>
> Hi
>
> Which version of OpenJPA are you building? Last month (IIRC) we removed the
> openjpa.loglevel property from the builds (1.2.x - trunk). If you have an
> older version of one of the pom.xml files it might still show up though.
>
> FWIW the changes were done under
> OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557>
> .
>
> -mike
>
> On Mon, May 17, 2010 at 5:54 AM, Web developer <webautomator2@gmail.com
> >wrote:
>
> > Got the following notice when trying to run tests:
> >
> > enhance.all.entities:
> > [echo] running enhancer
> > 160 WARN [main] openjpa.Runtime - The configuration property named
> > "openjpa.loglevel" was not recognized and will be ignored, although the
> > name
> > closely matches a valid property called "openjpa.Log".
> >
> > Logging not configured properly? John
> >
>
Re: Test run
Posted by Michael Dick <mi...@gmail.com>.
Hi
Which version of OpenJPA are you building? Last month (IIRC) we removed the
openjpa.loglevel property from the builds (1.2.x - trunk). If you have an
older version of one of the pom.xml files it might still show up though.
FWIW the changes were done under
OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557>
.
-mike
On Mon, May 17, 2010 at 5:54 AM, Web developer <we...@gmail.com>wrote:
> Got the following notice when trying to run tests:
>
> enhance.all.entities:
> [echo] running enhancer
> 160 WARN [main] openjpa.Runtime - The configuration property named
> "openjpa.loglevel" was not recognized and will be ignored, although the
> name
> closely matches a valid property called "openjpa.Log".
>
> Logging not configured properly? John
>
Fwd: Test run
Posted by Web developer <we...@gmail.com>.
---------- Пересланное сообщение ----------
От кого: Web developer <we...@gmail.com>
Дата: 27 мая 2010 г. 15:27
Тема: Re: Test run
Кому: Rick Curtis <cu...@gmail.com>
>Since there are multiple persistence units defined in the p.xml file that
you specified, we incorrectly try to create the >OPENJPA_SEQUENCE_TABLE
multiple times. Not that big of a deal.
Here is my updated persistence.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!--
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1.0">
<persistence-unit name="embeddables" transaction-type="RESOURCE_LOCAL">
<provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
<class>Address</class>
<class>ContactInfo</class>
<class>Phone</class>
<class>User</class>
</persistence-unit>
</persistence>
310 embeddables INFO [main] openjpa.jdbc.JDBC - Using dictionary class
"org.apache.openjpa.jdbc.sql.H2Dictionary".
385 embeddables INFO [main] openjpa.Runtime - Creating sequence table.
1814 embeddables TRACE [main] openjpa.jdbc.SQL - <t 644193719, conn
1498770706> executing stmnt 1260137319 CREATE TABLE OPENJPA_SEQUENCE_TABLE
(ID TINYINT NOT NULL, SEQUENCE_VALUE BIGINT, PRIMARY KEY (ID))
1826 embeddables TRACE [main] openjpa.jdbc.SQL - <t 644193719, conn
1498770706> [12 ms] spent
163 embeddables INFO [main] openjpa.Runtime - Starting OpenJPA
2.0.0-beta3
346 embeddables INFO [main] openjpa.jdbc.JDBC - Using dictionary class
"org.apache.openjpa.jdbc.sql.H2Dictionary".
Exception in thread "main" <openjpa-2.0.0-beta3-r422266:926797 fatal store
error> org.apache.openjpa.persistence.RollbackException: The transaction has
been rolled back. See the nested exceptions for details on the errors that
occurred.
at
org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:573)
at Main.init(Main.java:55)
at Main.main(Main.java:10)
Caused by: <openjpa-2.0.0-beta3-r422266:926797 fatal general error>
org.apache.openjpa.persistence.PersistenceException: The transaction has
been rolled back. See the nested exceptions for details on the errors that
occurred.
at
org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2279)
at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2122)
at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2020)
at
org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1938)
at
org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1462)
at
org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:924)
at
org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:556)
... 2 more
Caused by: <openjpa-2.0.0-beta3-r422266:926797 fatal general error>
org.apache.openjpa.persistence.PersistenceException: Таблица "USER0" не
найдена
Table "USER0" not found; SQL statement:
INSERT INTO User0 (id, user, user_name, city, state, street, zip, number,
type) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [42102-132] {INSERT INTO User0 (id,
user, user_name, city, state, street, zip, number, type) VALUES (?, ?, ?, ?,
?, ?, ?, ?, ?)} [code=42102, state=42S02]
at
org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4827)
at
org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4787)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:136)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:110)
at
org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:62)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:89)
at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:550)
at
org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:106)
at
org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59)
at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:103)
at
org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:743)
at
org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130)
... 9 more
Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Таблица
"USER0" не найдена
Table "USER0" not found; SQL statement:
INSERT INTO User0 (id, user, user_name, city, state, street, zip, number,
type) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?) [42102-132] {INSERT INTO User0 (id,
user, user_name, city, state, street, zip, number, type) VALUES (?, ?, ?, ?,
?, ?, ?, ?, ?)} [code=42102, state=42S02]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:237)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$000(LoggingConnectionDecorator.java:70)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection.prepareStatement(LoggingConnectionDecorator.java:289)
at
org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:186)
at
org.apache.openjpa.lib.jdbc.ConfiguringConnectionDecorator$ConfiguringConnection.prepareStatement(ConfiguringConnectionDecorator.java:155)
at
org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:186)
at
org.apache.openjpa.jdbc.kernel.JDBCStoreManager$RefCountConnection.prepareStatement(JDBCStoreManager.java:1639)
at
org.apache.openjpa.lib.jdbc.DelegatingConnection.prepareStatement(DelegatingConnection.java:175)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.prepareStatement(PreparedStatementManagerImpl.java:289)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:112)
at
org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:81)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:99)
at
org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:87)
... 16 more
Do not see changes with a single persistence unit in configuration. John
>The main method that you are calling isn't a main line path that most (if
>any) people go down.
>
> Do you have the property -Dopenjpa.jdbc.SynchronizeMappings=buildSchema
[2] specified anywhere? That property will automatically create the
necessary tables at runtime.
>
> If you're still having problems, I'd suggest putting together a coherent
question and posting it back to the users mailing list.
>
> Thanks,
> Rick
>
> [1] http://openjpa.apache.org/samples.html
> [2]
http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/manual.html#ref_guide_mapping_synch
>
>
Re: [OFF-LINE] Re: Test run
Posted by Web developer <we...@gmail.com>.
What else you need from me to explain? No mappings and sequence table
generated for ANY database. It looks like runtime tools might work. But
currently I am interested in external mapping configuration file for forced
processing via mapping tool rather *.java or *.bin file processing. In any
case I should care now only about manual mapping(no runtime). It just gives
me more guarantee against runtime features. John
P.S. Yes, I am still running samples. That's because batch tools in OpenJPA
still do not work. Otherwise I would already move to Salient.
2010/5/27 Rick Curtis <cu...@gmail.com>
> Please describe what you are trying to do?
>
> 2010/5/27 Web developer <we...@gmail.com>
>
>> Here is how I changed the runner configuration:
>>
>> -Dopenjpa.jdbc.SynchronizeMappings=buildSchema
>> -Dopenjpa.ConnectionDriverName=org.h2.Driver
>>
>> -Dopenjpa.ConnectionURL=jdbc:h2:/tmp/persist_backend
>> -Dopenjpa.DynamicEnhancementAgent=false
>> -Dopenjpa.RuntimeUnenhancedClasses=unsupported
>>
>> And here is the output:
>>
>> 212 embeddables INFO [main] openjpa.Runtime - Starting OpenJPA
>> 2.0.0-beta3
>> 483 embeddables INFO [main] openjpa.jdbc.JDBC - Using dictionary class
>> "org.apache.openjpa.jdbc.sql.H2Dictionary".
>> Exception in thread "main" <openjpa-2.0.0-beta3-r422266:926797 nonfatal
>> user error> org.apache.openjpa.persistence.ArgumentException: An error
>> occurred while parsing the query filter "SELECT u FROM User u , in
>> (u.addresses) a WHERE a.coordinates.longitude='38'". Error message: No field
>> named "coordinates" in "Address". Did you mean "city"? Expected one of the
>> available field names in "Address": "[city, state, street, zip]".
>> at
>> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.parseException(AbstractExpressionBuilder.java:119)
>> at
>> org.apache.openjpa.kernel.exps.AbstractExpressionBuilder.traversePath(AbstractExpressionBuilder.java:296)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getPath(JPQLExpressionBuilder.java:1941)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getPathOrConstant(JPQLExpressionBuilder.java:1861)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.eval(JPQLExpressionBuilder.java:1169)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getValue(JPQLExpressionBuilder.java:2054)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getValue(JPQLExpressionBuilder.java:2040)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.eval(JPQLExpressionBuilder.java:1055)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getExpression(JPQLExpressionBuilder.java:1970)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.eval(JPQLExpressionBuilder.java:997)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.evalWhereClause(JPQLExpressionBuilder.java:668)
>> at
>> org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder.getQueryExpressions(JPQLExpressionBuilder.java:297)
>> at org.apache.openjpa.kernel.jpql.JPQLParser.eval(JPQLParser.java:67)
>> at
>> org.apache.openjpa.kernel.ExpressionStoreQuery$DataStoreExecutor.<init>(ExpressionStoreQuery.java:733)
>> at
>> org.apache.openjpa.kernel.ExpressionStoreQuery.newDataStoreExecutor(ExpressionStoreQuery.java:171)
>> at
>> org.apache.openjpa.kernel.QueryImpl.createExecutor(QueryImpl.java:747)
>> at
>> org.apache.openjpa.kernel.QueryImpl.compileForDataStore(QueryImpl.java:705)
>> at
>> org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:687)
>> at org.apache.openjpa.kernel.QueryImpl.compile(QueryImpl.java:587)
>> at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:976)
>> at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:962)
>> at
>> org.apache.openjpa.persistence.EntityManagerImpl.createQuery(EntityManagerImpl.java:98)
>> at Main.runQueries(Main.java:21)
>> at Main.main(Main.java:11)
>>
>> After removing earlier mentioned option previous exception about
>> non-existing tables is gone. It looks like it really create something in
>> database. I will check later what is in H2 database. John
>>
>> 2010/5/27 Rick Curtis <cu...@gmail.com>
>>
>> Did you read my previous reply? In your previous emails you had two
>>> problems. The first problem[1] was because you were running TableJDBCSeq
>>> manually and there were multiple persistence units defined in your
>>> persistence.xml file. When you removed the other persistence units from that
>>> file, this problem went away. Correct?
>>>
>>> > Do you have the property -Dopenjpa.jdbc.SynchronizeMappings=buildSchema
>>> specified anywhere? That property will automatically create the necessary
>>> tables at runtime.
>>> Did you try this?
>>>
>>> >If you're still having problems, I'd suggest putting together a coherent
>>> question and posting it back to the users mailing list.
>>> Forwarding this string of emails onto the dev mailing list doesn't
>>> constitute a coherent question. You will receive a much better response with
>>> a well thought-out question.
>>>
>>> Thanks,
>>> Rick
>>>
>>> [1] CREATE TABLE OPENJPA_SEQUENCE_TABLE (ID TINYINT NOT NULL,
>>> SEQUENCE_VALUE BIGINT, PRIMARY KEY (ID)) [42101-132] {stmnt 1301078346
>>> CREATE TABLE OPENJPA_SEQUENCE_TABLE (ID TINYINT NOT NULL, SEQUENCE_VALUE
>>> BIGINT, PRIMARY KEY (ID))} [code=42101, state=42S01]
>>> org.apache.openjpa.lib.jdbc.ReportingSQLException: Таблица
>>> "OPENJPA_SEQUENCE_TABLE" уже существует
>>> Table "OPENJPA_SEQUENCE_TABLE" already exists; SQL statement:
>>> CREATE TABLE OPENJPA_SEQUENCE_TABLE (ID TINYINT NOT NULL, SEQUENCE_VALUE
>>> BIGINT, PRIMARY KEY (ID)) [42101-132] {stmnt 1301078346 CREATE TABLE
>>> OPENJPA_SEQUENCE_TABLE (ID TINYINT NOT NULL, SEQUENCE_VALUE BIGINT, PRIMARY
>>> KEY (ID))} [code=42101, state=42S01]
>>> at
>>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:257)
>>> at
>>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:241)
>>> at
>>> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:70)
>>> ......
>>>
>>> 2010/5/27 Web developer <we...@gmail.com>
>>>
>>>
>>>> >The main method that you are calling isn't a main line path that most
>>>> (if >any) people go down.
>>>> >
>>>> > Do you have the property
>>>> -Dopenjpa.jdbc.SynchronizeMappings=buildSchema [2] specified anywhere? That
>>>> property will automatically create the necessary tables at runtime.
>>>> >
>>>> > If you're still having problems, I'd suggest putting together a
>>>> coherent question and posting it back to the users mailing list.
>>>> >
>>>> > Thanks,
>>>> > Rick
>>>> >
>>>> > [1] http://openjpa.apache.org/samples.html
>>>> > [2]
>>>> http://openjpa.apache.org/builds/2.0.0/apache-openjpa-2.0.0/docs/manual/manual.html#ref_guide_mapping_synch
>>>> >
>>>> >
>>>>
>>>>
>>>
>>
>