By default, Glorp is using proxies for all attributes in relationship mappings.
See method: RelationshipMapping>>initialize.
This is fine and we would normally leave this enabled and resolve the proxy during postFetch.
However, using a pooled session repository provider this is not possible unless objects are somehow shared between sessions or by other means (not sure how).
I am documenting this with more unit tests and will soon submit the changes. I will also add more information to this issue.
Workaround for now, without disabling a session pool, is use relationship mappings for attributes with use of proxies disabled.
By default, Glorp is using proxies for all attributes in relationship mappings.
See method: RelationshipMapping>>initialize.
This is fine and we would normally leave this enabled and resolve the proxy during postFetch.
However, using a pooled session repository provider this is not possible unless objects are somehow shared between sessions or by other means (not sure how).
I am documenting this with more unit tests and will soon submit the changes. I will also add more information to this issue.
Workaround for now, without disabling a session pool, is use relationship mappings for attributes with use of proxies disabled.