[
https://issues.apache.org/jira/browse/CAUSEWAY-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059271#comment-18059271
]
Andi Huber commented on CAUSEWAY-3969:
--------------------------------------
In addition perhaps add a config option where this safeguard can be disabled,
for troubleshooting or when Devs know what they are doing.
Perhaps also provide some logging on discovered entities and their
corresponding weaving state (during app startup).
> [JPA] Fail early on inconsistent weave state within discovered entity type
> hierarchies
> --------------------------------------------------------------------------------------
>
> Key: CAUSEWAY-3969
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3969
> Project: Causeway
> Issue Type: Improvement
> Components: Persistence JPA
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> For every entity discovered, its entire type hierarchy (excluding interfaces)
> needs to be either byte-code enhanced or not. Mixed states may lead to
> unpredictable behavior. That is failures later at runtime affecting
> persistence related domain code.
> We want a safeguard at application launch, that checks every discovered JPA
> entity.
> (backport to v2 is desired)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
