[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482409
]
Abe White commented on OPENJPA-175:
---
+1, with some caveats:
- The proposed patch doesn't handle the common cases
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482411
]
Abe White commented on OPENJPA-168:
---
> when I am executing the 1st select I see 3 eagerKeys in the eagerKey map in
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482421
]
Abe White commented on OPENJPA-168:
---
Comments on the proposed patch:
- I don't like the whole scheme of setting t
AFIACT, the problem is that the openjpa.enhance.PCRegistry class
uses static
fields to store Meta information. When the second instance is
loaded, the
PCRegistry has been initialized, but doesn't contain that instance's
subclasses and an exception is thrown
The PCRegistry has to use static m
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482448
]
Michael Dick commented on OPENJPA-132:
--
I'm fine using Abe's patch. The patch I submitted was just focussed on
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482462
]
Kevin Sutter commented on OPENJPA-132:
--
Abe,
Can you post your patch so that we can see how the two approaches
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abe White resolved OPENJPA-132.
---
Resolution: Fixed
Fixed in SVN revision 520522. We can back out if we decide to use an
alternative
[
https://issues.apache.org/jira/browse/OPENJPA-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482484
]
Abe White commented on OPENJPA-132:
---
Sorry Kevin; I didn't see your comment before committing. As my resolution
[
https://issues.apache.org/jira/browse/OPENJPA-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482490
]
Ritika Maheshwari commented on OPENJPA-168:
---
Abe your comment :
- I don't like the whole scheme of settin
[
https://issues.apache.org/jira/browse/OPENJPA-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srinivasa Segu updated OPENJPA-175:
---
Attachment: OPENJPA-175-patch.txt
Patch with fixes to address the FetchBatchSize values of -
Abe White wrote:
>
>> AFIACT, the problem is that the openjpa.enhance.PCRegistry class
>> uses static
>> fields to store Meta information. When the second instance is
>> loaded, the
>> PCRegistry has been initialized, but doesn't contain that instance's
>> subclasses and an exception is thr
Marc,
Thanks for the pointers. Can you please answer the following set of questions?
1. The doc requires that "In order to enable automatic runtime mapping, you must
first list all your persistent classes". Is this true for EE case also?
2. Section "1.2.Generating DDL SQL" talks about .sql fi
Marina-
On Mar 20, 2007, at 4:02 PM, Marina Vatkina wrote:
Marc,
Thanks for the pointers. Can you please answer the following set of
questions?
1. The doc requires that "In order to enable automatic runtime
mapping, you must first list all your persistent classes". Is this
true for EE
Marc,
Marc Prud'hommeaux wrote:
Marina-
On Mar 20, 2007, at 4:02 PM, Marina Vatkina wrote:
Marc,
Thanks for the pointers. Can you please answer the following set of
questions?
1. The doc requires that "In order to enable automatic runtime
mapping, you must first list all your persisten
Marina-
They do in SE, but as there is no requirement to do it in EE,
people try to reduce the amount of typing ;).
Hmm ... we might not actually require it in EE, since we do examine
the ejb jar to look for persistent classes. I'm not sure though.
You should test with both listing them a
> They do in SE, but as there is no requirement to do it in EE, people
> try to reduce the amount of typing ;).
In EE, persistent classes can be specified via
a) explictly via
b) via one or more
c) via one or more
d) leave everything unspecified and OpenJPA will scan for @Entity
annotated cla
Marc,
Marc Prud'hommeaux wrote:
Marina-
They do in SE, but as there is no requirement to do it in EE, people
try to reduce the amount of typing ;).
Hmm ... we might not actually require it in EE, since we do examine the
ejb jar to look for persistent classes. I'm not sure though.
You s
Exception prefixes should be human-readable
---
Key: OPENJPA-176
URL: https://issues.apache.org/jira/browse/OPENJPA-176
Project: OpenJPA
Issue Type: Improvement
Components: diagnostics
Af
Marina-
Let me give it a try. How would the persistence.xml property look
like to generate .sql file?
Actually, I just took a look at this, and it look like it isn't
possible to use the "SynchronizeMappings" property to automatically
output a sql file. The reason is that the property take
Then I'll first start with an easier task - check what happens in EE if entities
are not explicitly listed in the persistence.xml file :).
thanks,
-marina
Marc Prud'hommeaux wrote:
Marina-
Let me give it a try. How would the persistence.xml property look
like to generate .sql file?
Actua
20 matches
Mail list logo
