[
https://issues.apache.org/jira/browse/OPENJPA-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vikram Bhatia updated OPENJPA-230:
--
Attachment: testcase.zip
JUnit testcase.
Handle guaranteed delivery of Data Cache events on
Hi Philippe,
It looks like your attachment was dropped by the mailing list so I'm
guessing a little here. I did try setting all of this up from scratch with
one of my Eclipse projects, here's what I did.
Downloaded openjpa-project-0.9.7-incubating-source.zip and
@DiscriminatorColumn(discriminatorType=DiscriminatorType.CHAR)
@DiscriminatorValue(value=S)
The discriminator type is CHAR but the value is a String. How about
declaring the type as STRING of length 1?
@DiscriminatorColumn(discriminatorType=DiscriminatorType.STRING,
length=1)
Pinaki Poddar
[
https://issues.apache.org/jira/browse/OPENJPA-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Prud'hommeaux resolved OPENJPA-237.
Resolution: Fixed
Fix Version/s: 0.9.8
Committed patch.
Value.setAliases
Marc Prud'hommeaux wrote:
I think this is a very worthwhile project. James and a few others
excoriated me about this issue over beers after JavaOne last week,
and, while the bruises from their rhetorical assault are still
healing, their observations about the comparative out of
djencks wrote:
James,
Could extract from this verbiage the scenarios you'd like supported?
The simplest scenario is, take any maven 2 project which is using hibernate.
Switch the hibernate jars to openjpa jars edit the bits of the
persistence.xml that are required and have things work
Patrick Linskey-2 wrote:
How hard is it to add a reflection/cglib type alternative to the upfront
bytecode generation (like hibernate does) to save us from the
development-time pain?
Not particularly hard. There are a few APIs that would break for some
cases, but it's even pretty
Hi,
There are semi-related problems with the Discriminator support documented in
OPENJPA-143. It seems that if we veer away from the string-based
discriminators, then we still have a few problems... Sorry, no answers at
the moment. Just sharing the pain...
Kevin
On 5/21/07, Pinaki Poddar
Sorry to show my ignorance, but what are historical objects? Thanks!
Kevin
On 5/18/07, Ricardo Andere de Mello [EMAIL PROTECTED] wrote:
ok, I'm sending this message to netmind list too, so they can answer my
next
question too:
* Maybe this is a silly question, but is it possible to place
OpenJPA Community,
So, is this XML Mapping support interesting to the community? Catalina has
been working on a solution for this O/Xml Mapping support and is looking for
interest from the community for discussion purposes before possibly
contributing it to OpenJPA. We can provide more detail
I hope the bruises heal soon btw :)
Time heals all wounds. At least, that's what I'm told.
On May 21, 2007, at 10:09 AM, James.Strachan wrote:
Marc Prud'hommeaux wrote:
I think this is a very worthwhile project. James and a few others
excoriated me about this issue over beers
I'd really appreciate it if a committer could take a look at the
second patch I supplied for openjpa-148. The first patch introduced
frequent NPEs which the second patch fixes. The second patch also
handles some cases in which a directory to scan is supplied as a file
URL. I think that
[
https://issues.apache.org/jira/browse/OPENJPA-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497575
]
Marc Prud'hommeaux commented on OPENJPA-148:
I've gone ahead and applied OPENJPA-148-2.patch. If this
[
https://issues.apache.org/jira/browse/OPENJPA-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497601
]
Patrick Linskey commented on OPENJPA-130:
-
Ignacio Andreu will be working on this issue for the Google
yes this look something simple, but it is not...
see, objects exists in time, so for example, they are not deleted, they are
finalized.
the worst part are the relationships, because they are historical too...
basically you have a start and end date for that object, and the object with
end
As I've had it explained to me, you would not choose the time in a
user-generated or user-visible query. Instead, the user would set the
time and associate it with an EntityManager. The time is invisible to
normal entity operations, including queries. For each query for a
temporal object
[
https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497624
]
Patrick Linskey commented on OPENJPA-243:
-
The plugin as of r540340 integrates the OpenJPA enhancer with
[
https://issues.apache.org/jira/browse/OPENJPA-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497626
]
Patrick Linskey commented on OPENJPA-243:
-
One missing instruction from the previous comment: the 0.1
18 matches
Mail list logo
