Dynamic FetchPlans are now among my new favorite things (except now, I
need to rewrite a lot of code to remove my fake entity hacks).
I will definitely try to put together a sample (and blog posting, and
wiki entry on Geronimo site).
Jay
Pinaki Poddar wrote:
> Hi,
> I like what you are doing a
Hi,
I like what you are doing and believe that it is a predominant use case for
multi-tier for OpenJPA/JPA based web applications.
Please consider writing up a small, self-contained sample (preferably without
the application server scaffolding) to demonstrate your solution to integrate
JA
Thanks for the hint.
The setting you suggested caused deployment errors for me (I am
deploying my app to Geronimo 2.1.3 which uses OpenJPA 1.0.3).
But, it looks like this setting will work for me:
The only strange thing is that my unloaded booleans show up in XML as
being false (rather than no
> If I set the DetachState to something else, would I be able to get it
> to simply return blanks/nulls for the unloaded fields?
Try :
-
Pinaki Poddar http://ppoddar.blogspot.com/
http://www.linkedin.com/in/pinakipoddar
OpenJPA P
Thank you for the additional insight.
Switching the DetachState is making things more clear. I had it set
to a value of "all" before based on some example (not sure where from
though).
Here are answers to your questions - Hopefully by the time I finish
answering them all, I will have it working.
Hi,
You are correct in detaching the instance with the current fetch plan. In
theory, now the detached instance should only have the fields selected by the
fetch plan. If that is not happening then verify the following in order
1. Is the instance detached? OpenJPAEntityManager.isDetached(pc)
There was a typo I just noticed.
The first line of my email was supposed to read:
> I have been banging my head against FetchPlans, and all of my attempts
> have returned either an exception -OR- the default plan.
Hopefully that didn't cause any confusion.
Jay
Jay D. McHugh wrote:
> Hello agai
Hello again,
I have been banging my head against FetchPlans, and all of my attempts
have returned either an exception of the default plan.
In an attempt to really restrict what is comming back I came up with the
following:
OpenJPAEntityManager em = OpenJPAPersistence.cast(entityManager);
FetchP
Hi,
You can look in OpenJPA documentation [1][2] and if you have access to the
source code (we are open source:) then take a look at Test cases [3]
[1]
http://openjpa.apache.org/builds/latest/docs/manual/manual.html#ref_guide_runtime_jpafetch
[2]
http://openjpa.apache.org/builds/latest/docs
Thanks for suggesting FetchPlan.
Is there a reference that you could suggest on finding out more about
FetchPlan - preferably with examples?
Thanks in advance,
Jay
Pinaki Poddar wrote:
> Hi,
>> I have a whole hierarchy of entities that I am transforming using JAXB
>> to send XML to a browser cl
Hi,
> I have a whole hierarchy of entities that I am transforming using JAXB
> to send XML to a browser client. But, the amount of detail that I am
> sending as XML changes depending on the type of request.
OpenJPA's dynamic FetchPlan is the correct solution for such use case. With
FetchPlan
Hello all,
I have what may be a strange requirement (I guess you will have to
decide on that). But, there is a fairly long amount of background
before you get to my actual question.
Background -
I have a whole hierarchy of entities that I am transforming using JAXB
to send XML to a browser clien
12 matches
Mail list logo
