[
https://issues.apache.org/jira/browse/CAY-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472729#comment-17472729
]
Andrus Adamchik commented on CAY-2728:
--------------------------------------
In this logic we followed JPA in making "Serializable" the fallback type. So
all the confusing exceptions are due to that choice. Maybe we can rethink this
part?
> Add special ExtendedType to generate user-friendly exceptions
> -------------------------------------------------------------
>
> Key: CAY-2728
> URL: https://issues.apache.org/jira/browse/CAY-2728
> Project: Cayenne
> Issue Type: Improvement
> Components: Core Library
> Affects Versions: 4.2.B1
> Reporter: Nikita Timofeev
> Assignee: Nikita Timofeev
> Priority: Minor
> Fix For: 4.2.B2
>
>
> We have some internal values that could be used in a DB query and cause
> exceptions. In that case all the information user get is a confusing message
> like this: "{{Haven't found suitable ExtendedType for class
> 'org.apache.cayenne.access.flush.IdGenerationMarker'}}". See CAY-2726 for
> example.
> We should add some special {{ExtendedType}} to handle those types and
> generate user-friendly exceptions.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
