Yes, you are right, the cache key can't be done as I suggested.
Further, I have looked into why there is a Module assigned into the
EntityStoreUnitOfWork, and it boils down to, as usual, to the
deserialization of entities. It basically needs to know where to look for
the entity types.
And that is
Hmmm interesting problem . Could it be reproduced with something like this:
a. Creation of a UnitOfWork
b. Accessing entity M1 in module M
c. Entity E calls service MS in module M.
d. Service uses entity N1 in module N (N1 has some sort of shared visibility)
(later in the same UOW)
e. Someone
[
https://issues.apache.org/jira/browse/ZEST-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599692#comment-14599692
]
Paul Merlin commented on ZEST-25:
-
Gang,
The build should now produce almost good source and
[
https://issues.apache.org/jira/browse/ZEST-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Merlin updated ZEST-25:
Description:
Apache Software Foundation releases Source Tarballs only.
Our build system builds a source tarbal
Follow-up; The case when it gets wrong is more complex than my list, and I
am not able to create a testcase for this...
On Wed, Jun 24, 2015 at 10:51 PM, Niclas Hedhman wrote:
> Gang,
>
> I have found a fairly sophisticated bug, which is rather severe and
> possibly hard to fix without breaking
Sounds good to me.
Niclas Hedhman a écrit :
> Gang,
> for a very long time, it has bothered me that the
> EntityTypeNotFoundException is too "barren", one get to know the type is
> not visible, but often it is hard to see "why".
>
> So, I have added that it reports "from" which module, and what en
Gang,
I have found a fairly sophisticated bug, which is rather severe and
possibly hard to fix without breaking applications, that might depend on
wrong behavior...
It manifests itself as not having the right Visibility of entities, and the
reason is because the EntityStoreUnitOfWork may be set u
Gang,
for a very long time, it has bothered me that the
EntityTypeNotFoundException is too "barren", one get to know the type is
not visible, but often it is hard to see "why".
So, I have added that it reports "from" which module, and what entity types
can be seen from there.
Since this exception
