I'm trying to study for the SCBCD exam and am working through some examples to try and get up to speed on JPA. I have some behavior that doesn't make sense to me and I'm hoping you guys can shed some light on it. I'm working through a lazy loading, one-to-many example. I have 2 classes, Fly and FlyBox. FlyBox has a one-to-many unidirectional relationship to Fly that is lazy loaded. Here are relevant snippets of each's code:
I have a stateless session bean that is retrieving a FlyBox and using a left fetch join to also retrieve the associated Fly records for a given FlyBox id. Here is the following Stateless session bean code:
My problem is, is that the number of results returned for a single FlyBox query are proportional to the number of Fly records that particular fly box has (and thus breaks this code). For instance, if I have a FlyBox that has 4 Fly records associated with it, the query will return that same FlyBox record 4 times. If I have a FlyBox with 2 Fly records, the above query attempts to return that FlyBox 2 times.
FYI, if I change the fetch type to eager and remove the fetch join portion of the query, everything is returned appropriately.
What am I missing?
Thanks in advance.
Joined: May 20, 2008
LOL, look around enough and you'll find an answer. The following query solves my issue:
However, I'm still not sure why my query functioned the way it did before I added DISTINCT OBJECT. Any info is appreciated.
How do you know it's returning the same Flybox each time?
Could it be putting proxies in place of the records, and you're just looking at the proxies, which by nature, could all be the same? That would make sense for lazy loading.
Joined: May 20, 2008
I am inspecting the objects in the debugger and they all have the same primary key but are all unique instances (memory addresses). I only have one FlyBox in the database so I know there aren't more than 1.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com