[
https://issues.apache.org/jira/browse/OPENJPA-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574020#action_12574020
]
Sakari Maaranen commented on OPENJPA-227:
-
This is a particularly annoying bug wit
[
https://issues.apache.org/jira/browse/OPENJPA-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573989#action_12573989
]
Matthew Kelm commented on OPENJPA-294:
--
SeYoul, the example you were referring to nee
ManagedClassSubclasses stores table names twice.
-
Key: OPENJPA-529
URL: https://issues.apache.org/jira/browse/OPENJPA-529
Project: OpenJPA
Issue Type: Bug
Reporter: Michael Dick
FK columns which contain reserved workds are renamed incorrectly.
-
Key: OPENJPA-528
URL: https://issues.apache.org/jira/browse/OPENJPA-528
Project: OpenJPA
Issue Type: Bug
Well, if you specify your persistent classes in the properties, then
you don't need to specify them on the command line.
Otherwise, just properties. There are a few properties that influence
OpenJPA enhancer behavior.
-Patrick
On Fri, Feb 29, 2008 at 9:51 AM, Geir Magnusson Jr. <[EMAIL PROTECTED
That fixed it. Thanks.
What's the point of telling it about the properties file? Just
properties?
geir
On Feb 29, 2008, at 12:38 PM, Patrick Linskey wrote:
How about adding it to your exclude list? Per that set of includes and
excludes, the abstract class will be enhanced.
-Patrick
On
Nice machine name, btw.
-Patrick
On Fri, Feb 29, 2008 at 9:38 AM, Patrick Linskey <[EMAIL PROTECTED]> wrote:
> How about adding it to your exclude list? Per that set of includes and
> excludes, the abstract class will be enhanced.
>
> -Patrick
>
>
>
> On Fri, Feb 29, 2008 at 9:25 AM, Geir Magn
How about adding it to your exclude list? Per that set of includes and
excludes, the abstract class will be enhanced.
-Patrick
On Fri, Feb 29, 2008 at 9:25 AM, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
>
> On Feb 29, 2008, at 12:13 PM, Patrick Linskey wrote:
>
> >> How can I tell OpenJPA to
oh - fantastic! Thanks
On Feb 29, 2008, at 12:24 PM, Patrick Linskey wrote:
You might want to try setting the openjpa.OrphanedKeyAction to
"exception" -- this might help debug where the issue is coming from.
-Patrick
On Tue, Feb 26, 2008 at 5:22 PM, Geir Magnusson Jr. <[EMAIL PROTECTED]>
w
On Feb 29, 2008, at 12:13 PM, Patrick Linskey wrote:
How can I tell OpenJPA to ignore it?
Don't ask OpenJPA to enhance it.
How are you invoking the enhancer? It sounds like you're either
specifying a list of classes to enhance, including the new superclass,
or you're specifying nothing, and
You might want to try setting the openjpa.OrphanedKeyAction to
"exception" -- this might help debug where the issue is coming from.
-Patrick
On Tue, Feb 26, 2008 at 5:22 PM, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
> We're getting tons of these in production (and in test). OpenJPA
> 1.0.1
> How can I tell OpenJPA to ignore it?
Don't ask OpenJPA to enhance it.
How are you invoking the enhancer? It sounds like you're either
specifying a list of classes to enhance, including the new superclass,
or you're specifying nothing, and the new superclass is listed in your
persistence.xml.
After a bit of refactoring, I have a set of entity classes that have a
common abstract ancestor. This ancestor has nothing JPA-ish about it.
However, when I run the enhancer (v1.0.2) I get :
[openjpac] 1003 pu WARN [main] openjpa.Enhance - Type "class
com.joost.model.codes.AbstractCont
13 matches
Mail list logo