Hello Ivy Team, In my project, I had to switch from the default Eager loading to the Lazy loading of the Entity classes. The reason was that the queries were not optimized. Now I have the following problem, every time I try to inspect the variables in debug mode, the Designer is throwing errors and it is almost impossible for debugging: Best Regards, Yordan Yunchov asked 21.12.2016 at 09:19 Stelt0 Flavio Sadeghi ♦♦ |
[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.
answered 21.12.2016 at 15:49 Flavio Sadeghi ♦♦ 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
(22.12.2016 at 09:31)
Stelt0
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.
(22.12.2016 at 10:00)
Flavio Sadeghi ♦♦
Thanks a lot for addressing this issue ! Good luck ! :)
(22.12.2016 at 10:05)
Stelt0
@Stelt0, We have fixed this bug for 6.5, which will be released very soon (probably tomorrow).
(19.01.2017 at 09:39)
Flavio Sadeghi ♦♦
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 ?
(19.01.2017 at 12:25)
Stelt0
We can fix it for 6.0. (6.1 not, since it is a Leading Edge version) Would this help?
(19.01.2017 at 12:28)
Flavio Sadeghi ♦♦
showing 5 of 6
show 1 more comments
|
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 21.12.2016 at 09:19
Seen: 2,222 times
Last updated: 19.01.2017 at 12:28