Answers to: Eager Loading

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Thu, 19 Jan 2017 12:28:40 -0500

We can fix it for 6.0. (6.1 not, since it is a Leading Edge version) Would this help?

Comment by Stelt0 on Flavio Sadeghi's answer

Stelt0 — Thu, 19 Jan 2017 12:25:19 -0500

Thanks a lot Flavio ! is it possible to provide some hot-fix jar(s) that will work with older versions 6.0. and 6.1 ?

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Thu, 19 Jan 2017 09:39:53 -0500

@Stelt0, We have fixed this bug for 6.5, which will be released very soon (probably tomorrow).

Comment by Stelt0 on Flavio Sadeghi's answer

Stelt0 — Thu, 22 Dec 2016 10:05:00 -0500

Thanks a lot for addressing this issue ! Good luck ! :)

Comment by Flavio Sadeghi on Flavio Sadeghi's answer

Flavio Sadeghi — Thu, 22 Dec 2016 10:00:08 -0500

Thanks for feedback. I will check that. Probably the debugview can not handle java proxy objects, which are ordinarily used when working with lazy-loading. We can/will fix that. You will hear from me here.

Comment by Stelt0 on Flavio Sadeghi's answer

Stelt0 — Thu, 22 Dec 2016 09:31:21 -0500

Hello @Flavio Sadeghi,

I agree about what you said.

However, from the perspective of an user, if I can inspect the variables in Debug mode, why I can't inspect them in Ivy designer process development mode? There is always a error thrown. For me it is a product bug. And it is a big one. Why throwing and error ? Why not showing null or whatever ? I am not able to inspect the rest of the "unmanaged" variables as well. No mater where I click I get an error. Best Regards, Yordan

Answer by Flavio Sadeghi

Flavio Sadeghi — Wed, 21 Dec 2016 15:49:08 -0500

[Edit]: The Bug 'Label Job has encountered a problem' is fixed with 6.5. We return null, since the below explanation is still true.

Lazy evaluation of entity beans is not supported with the ivy persistency.

As described in the documentation, ivy persistency always works with unmanaged entity beans. Lazy loading is only supported with managed entity beans. A beans is managed as long the referenced session (link to the db/transaction) is open - means the entity is managed (i.e. cached) in the session.

How to solve:

Example: Table Company has a 1:n relation to Invoices.

First question: is the lazy loading required? Do the Company entity need a list of all invoices or can it be replaced/reduced to the @ManyToOne relation on the Invoice entity?
To get the list of all invoices of a company a repositoy method has to be implemented, e.g. InvoiceRepository.readAllOfCompany(Company c) : List< Invoices >;
Write own repository method and open/close the session inside this method. As long the session is open, as long the entiries are managed and lazy loading is supported. Always ensure with a try-finally block that the session gets closed. Otherwise, the connection to the database remains open and the allowed number of connections is limited. An example could be find here.