I posted this question before but I am now seeing it in several places and can
produce a test case for it. Here are two related classes (one-to-many) attribute
and attributeType, each with table/class inheritance.
Attribute class:
package ca.BidSpec.emall.categories;
import javax.persistence.Bas
Here is a scenario that shows odd behaviour, I want to see if it is expected or
not. The docs are not clear on it
If I have a many to one relationship for objects Store to Store Type and I
create a new Store and assign it to an existing Store type does this
relationship have to have cascasdeType.p
I think that I'm about +0.5 for TLP graduation. It seems to make more
sense, and from what I understand, there is only a minimal amount of
additional work involved. As the +0.5 indicates, I could be swayed the
other direction though.
-Patrick
--
Patrick Linskey
BEA Systems, Inc.
[
https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491104
]
Patrick Linskey commented on OPENJPA-219:
-
I agree about the mem leak problem in the patch that I created; h
On Apr 23, 2007, at 2:58 PM, Marc Prud'hommeaux wrote:
I'm personally rather neutral on whether OpenJPA should be a TLP
vs. a sub-project. TLP seems like it allows us more flexibility and
independence, so by default I would lean towards being a TLP.
That's my main concern as well.
Howe
I can toggle this exception on/off by adding the schema statement. I was running
validate on my country class that persists to the country table on a
table-per-class inheritance strategy. Using 0.9.6 openJPA
16 TRACE [main] openjpa.Runtime - Setting the following properties from
"file:/C:/BidSpe
I agree that it's nice to have an out-of-the-box database shipped
with our distribution.
Once Java SE 6 is universal, we can revisit the decision, since Java
SE 6 distributes Java DB (a renamed Derby distribution).
Craig
On Apr 23, 2007, at 3:03 PM, Kevin Sutter wrote:
Derby provides a ni
Derby provides a nice "out of the box" experience, so I vote to keep it with
our set of required runtime libraries.
On 4/18/07, Michael Dick <[EMAIL PROTECTED]> wrote:
In general I agree with Patrick. I'm +0 regarding including Derby, it's
nice
for the examples, but it just doesn't seem right t
[
https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491078
]
Bret Weinraub commented on OPENJPA-219:
---
I will add the "Cache v2" version here shortly.
> Reflection: negati
I'm personally rather neutral on whether OpenJPA should be a TLP vs.
a sub-project. TLP seems like it allows us more flexibility and
independence, so by default I would lean towards being a TLP.
However, I do notice that the DB TLP already holds other similar
projects (Torque, OJB, and Ap
[
https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491077
]
Bret Weinraub commented on OPENJPA-219:
---
I developed a patch version that cached both "success" and "failure"
OpenJPA has done a great job of forming a diverse community around a
great code base whose IP has been reviewed and approved for release,
and we're now a well-functioning, project in the incubator. So we are
now at the stage when we should think about when and how to leave the
incubator and
[
https://issues.apache.org/jira/browse/OPENJPA-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491038
]
Abe White commented on OPENJPA-219:
---
If we're going to cache, I don't see why we wouldn't cache the declared
fiel
Phill-
It sounds like a bug, but it would help to know what the exception
was :)
On Apr 23, 2007, at 7:02 AM, Phill Moran wrote:
I have been working with the validate tool and was getting an
exception on
classes that used @table(name="XXX", schema="YYY"). If I took out
the schema
porti
I have been working with the validate tool and was getting an exception on
classes that used @table(name="XXX", schema="YYY"). If I took out the schema
portion the exception went away. I see no mention of not using schema in @table
for validate use. Is this a bug or undocumented feature
The mappi
Marc,
I have several relationships that have the same target.
(table names and relationships follow)
class -(M-1)-> xClassAttrib -(1-1)-> attrib
component -(M-1)-> xCompAttrib -(1-1)-> attrib
Both of these end up at the same attrib table.
Could this be a problem?
I added some other 1-M rela
Marc,
This is nice! I like it. Whatever works for "easy" consumption (as far as
distribution goes) works for me.
Kevin
On 4/22/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
All-
The people at yWorks have graciously provided OpenJPA with an open-
source license to use their UML-generatin
17 matches
Mail list logo
