Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cascading throws IllegalArgumentException when attempting to merge LazyLoadingProxy #248

Closed
ledsoft opened this issue Jun 17, 2024 · 0 comments · Fixed by #249
Closed

Cascading throws IllegalArgumentException when attempting to merge LazyLoadingProxy #248

ledsoft opened this issue Jun 17, 2024 · 0 comments · Fixed by #249
Labels
bug
Milestone
2.0.1

Comments

@ledsoft
Copy link
Contributor

ledsoft commented Jun 17, 2024

When the client attempts to, for example, merge an already managed instance that cascades merging on a lazily loaded attribute, JOPA throws java.lang.IllegalArgumentException: OWLClassE_LazyLoadingProxy is not a known entity in this persistence unit.

JOPA cascading should be able to recognize lazy loading proxy and skip its processing.
@ledsoft ledsoft added the bug label Jun 17, 2024
@ledsoft ledsoft added this to the 2.0.1 milestone Jun 17, 2024
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Add test reproducing the issue.
d34dd59
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Ignore merge cascading of lazy loading proxy instances.
6e2869c
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Handle cascade refresh/detach w.r.t. lazy loading proxies.
22312fd
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Handle cascade remove w.r.t. lazy loading proxies.
dfd90df 
Remove cascading on lazily loaded relationship triggers loading and then cascades the remove operation.
@ledsoft ledsoft mentioned this issue Jun 17, 2024
Merged
@ledsoft ledsoft linked a pull request Jun 17, 2024 that will close this issue
Bug#248 cascade lazyloadingproxy #249
Merged
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Add test reproducing the issue.
8f49499
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Ignore merge cascading of lazy loading proxy instances.
7764609
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Handle cascade refresh/detach w.r.t. lazy loading proxies.
8c326bc
ledsoft added a commit that referenced this issue Jun 17, 2024
@ledsoft
[Bug #248] Handle cascade remove w.r.t. lazy loading proxies.
75022b8 
Remove cascading on lazily loaded relationship triggers loading and then cascades the remove operation.
@ledsoft ledsoft closed this as completed Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
2.0.1
Development

Successfully merging a pull request may close this issue.

Bug#248 cascade lazyloadingproxy kbss-cvut/jopa
1 participant
@ledsoft