This content has been marked as final. Show 2 replies
I don't have a complete resolution for this problem but I wanted to let you know that we're working on it and are able to reproduce it. It is a JE bug -- this behavior is not intentional. I will let you know as soon as we have a full resolution, which should be in the next several days.
Thanks for reporting this.
Another update: I have identified the problem internally and confirmed that bumping the version of the Entity class is a safe workaround.
The fix is still to come, but the workaround is safe.