Hi
First I don't know why there is no useful document on these sort of
listeners and how to use it.
Second after toiling I was able to find dirty fields and fire the pre-update
event. This is for a logging service we have to implement for our
application but now the problem is that if you want
https://issues.apache.org/jira/browse/OPENJPA-953, ok? - What happens next? ;-)
-Original Message-
From: Fay Wang [mailto:fyw...@yahoo.com]
Sent: Wednesday, March 04, 2009 6:08 AM
To: users@openjpa.apache.org
Subject: RE: ArrayIndexOutOfBoundsException in
org.apache.openjpa.util.Applic
I now use the openjpa-maven-plugin to enhance my persistence-enabled classes,
but I have a couple of projects which rely on a superclass, which needs
enhancing and testing.
I put this in a seperate project and wrote some unit tests for it, which needed
a few real entity beans to demonstrate pa
Adam,
Just to clarify this is also using version 1.0 of the plugin? I dont
think is supported if so. Did you try this?
${build.testOutputDirectory}/org/permacode/atomic/domain/entity/*.class
Just checking before I diagnose for you,
Randy
Adam Hardy wrote:
I now use the openjpa-maven-pl
Randy Watler on 04/03/09 14:28, wrote:
Just to clarify this is also using version 1.0 of the plugin? I dont
think is supported if so. Did you try this?
${build.testOutputDirectory}/org/permacode/atomic/domain/entity/*.class
Just checking before I diagnose for you,
Yes, I mean 1.1-SNA
Hi,
The JPA specification defines several listeners which can be configured via
orm.xml or annotations in your entity classes. Here's a quick view of the
available listeners :
The following annotations are defined to designate lifecycle event callback
methods of the corresponding
types.
• PrePersi
Hi,
This seems more like a question for the EJB container, rather than the JPA
provider, unless I've misunderstood what you're asking. Which application
server are you using?
-mike
On Wed, Mar 4, 2009 at 1:45 AM, is_maximum wrote:
>
> Hello
>
> I have a problem when I want to lookup my session
> However it might make for an interesting feature.
Yes. These are the sort of features that helps distinction of one vendor
from the other. Kodo has it, but these features were not available when
OpenJPA was seeded from Kodo codebase.
FilterListeners for ORDER BY clauses are still active, and c
Adam,
If I understood your problem correct, then you have a
.) module A which contains @Entities in src/test/java
.) module B which also has @Entities in src/test/java and rely on the @Entities
from module A
Is this the scenario you have?
If so, you need to tell module A that it should packa
Randy,
is supported in openjpa-maven-plugin-1.0
See
http://fisheye.codehaus.org/browse/mojo/tags/openjpa-maven-plugin-1.0/src/main/java/org/codehaus/mojo/openjpa/AbstractOpenJpaMojo.java?r=9091#l50
LieGrue,
strub
--- Randy Watler schrieb am Mi, 4.3.2009:
> Von: Randy Watler
> Betreff: R
Adam,
I stand corrected. Let me take a look for you.
Randy
Adam Hardy wrote:
Randy Watler on 04/03/09 14:28, wrote:
Just to clarify this is also using version 1.0 of the plugin? I
dont think is supported if so. Did you try this?
${build.testOutputDirectory}/org/permacode/atomic/domain/
IMHO, Spring should be logging the warning message, not OpenJPA. Registering
a class transformer is defined explicitly by the spec and OpenJPA shouldn't
be catching exceptions coming from 'Spring features' (The spec is pretty
huge, so please correct me if I'm wrong).
Also, I don't think that it
Hi Mark,
not quite.
I have module A with one Entity in src/main/java and several test entities which
extend it (to allow testing) in src/test/java.
I have moduleB which relies on moduleA non-test normal jar. I don't need the
test entities outside moduleA.
Therefore I created 2 executions -
No problem! I'm just glad someone's willing to look at it. I answered Mark
Struberg's message - although I didn't say much more than I've said already.
Randy Watler on 04/03/09 15:31, wrote:
Adam,
I stand corrected. Let me take a look for you.
Randy
Adam Hardy wrote:
Randy Watler on 04/03/0
Humm this is because the OpenJpaEnhancerMojo has
@requiresDependencyResolution compile
LieGrue,
strub
--- Adam Hardy schrieb am Mi, 4.3.2009:
> Von: Adam Hardy
> Betreff: Re: OpenJPA Maven Plugin
> An: users@openjpa.apache.org
> Datum: Mittwoch, 4. März 2009, 17:36
> Hi Mark,
>
> not quite.
I converted my project over from java.util.Date to java.sql.Timestamp for entity
fields after I figured that would give me more room to maneuver with a new
requirement for time fields.
It went smoothly with OpenJPA and made the MVC layer's type converter code a
cinch to refactor.
However I
Maven won't let me override that annotation in my execution config then?
Mark Struberg on 04/03/09 16:45, wrote:
Humm this is because the OpenJpaEnhancerMojo has
@requiresDependencyResolution compile
LieGrue,
strub
--- Adam Hardy schrieb am Mi, 4.3.2009:
Von: Adam Hardy
Betreff: Re: OpenJ
Adam,
After rereading Matt's question and your original problem report, I
believe you are asking how to get the target/test-classes directory
within a single project added to the class path used to invoke the
enhancer. By default, the existing target/classes directory is included,
but not tar
Sorry... I meant Mark!
Mark, let me know if you want me to submit a patch.
Randy
Randy Watler wrote:
Adam,
After rereading Matt's question and your original problem report, I
believe you are asking how to get the target/test-classes directory
within a single project added to the class path
Hi Michael,
As far as I know these are entity listener and we have to declare our
listener for each entity and I think this is not a good idea. consider that
we have nearly 30 entities and it may be added in the future we don't like
to declare a listener for each pre-update, pre-remove and pre-pe
Yes you're right, Now that I think about it I really don't know why I post
this question here!!! Perhaps it is because we are using OpenEJB and I made
a mistake in similar names :)
thanks for your reply
Michael Dick wrote:
>
> Hi,
>
> This seems more like a question for the EJB container, rat
Hi,
I think I understand your concern. You're looking for a default set of
listeners which apply to all your entities. This is also supported by the
JPA specification. Relevant section :
3.5.7.2 Specification of the Binding of Entity Listener Classes to Entities
The entity-listeners subelement of
Hi Adam,
Looks like we're less stringent about the @Temporal annotation. I'd have to
look closer to see that's the case.
Regarding the JPA 2.0 spec you can find a copy of the public review draft
here http://jcp.org/aboutJava/communityprocess/pr/jsr317/index.html
-mike
On Wed, Mar 4, 2009 at 10:
Well so we can define a listener for all the entities.
that's pretty good but one more question is that if we use these entity
listeners, can we still find out those fields that has been changed (dirty
fields) for example in pre-update and persist the result in DB. As far as I
know, inside the ca
Thanks Mike.
Looks like the same wording in JPA 2.0 too.
Regards
Adam
Michael Dick on 04/03/09 19:39, wrote:
Hi Adam,
Looks like we're less stringent about the @Temporal annotation. I'd have to
look closer to see that's the case.
Regarding the JPA 2.0 spec you can find a copy of the public r
Hi,
I have a table A with column COL1 of type java.lang.Long, i am joining this
in a OneToMany relationship using ElementJoinColumn annotation with COL2 of
table B which is a String data type. OpenJPA is throwing an error while
validating the metadata saying the datatype is incompatible. Is there
Hey pinaki, thanks for the comment, sorry for the late response...
I did'nt try build-time anhancement, cause I found sort of solution. I found
out that refresh() works a bit different, therefore when I first handle a
new entity, I do em.refresh(entity) and the entity's fields are fully
updated af
I minimized the places I get EntityNotFoundException to a single refresh
line.
I just can't figure out what the problem is:
if (!em.contains(entity))
return;
em.refresh(entity); -> EntityNotFoundException sometimes...
What do I do wrong? How can I tell that the entity is not m
28 matches
Mail list logo
