[
https://issues.apache.org/jira/browse/OPENJPA-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865919#action_12865919
]
Pinaki Poddar commented on OPENJPA-1612:
----------------------------------------
Rick,
In my view, this is not a change in the right direction.
OpenJPA used to have a reasonably advanced support for untyped relations. These
capabilities are described in [1]
Now in the past, I had used these powerful features to demonstrate how
generically typed structures can be modeled [2] in OpenJPA (that blog
unfortunately has been eaten by a very powerful company and one can merely find
its indirect cached references by searching for 'Persistence of Generic Graph
Pinaki Poddar" ;).
Recently I noticed that those powerful type system is weakened (meaning those
neat generic model example does not work with OpenJPA 2.0).
Support for generically typed domain model is a powerful construct and OpenJPA
was quite capable of meeting that demand. Hence I consider OpenJPA 2.0 has
regressed on that aspect.
I have not investigated deeply, but my cursory look at the changes suggest that
cause of the regression is more at the surface and can be corrected at ease.
In view of that observation, I see this current commit as a step backward. And
I hope that the original committer will consider rolling the change back.
[1] will provide the user sufficient choices on how to persist Object o -- when
it is assigned to a Persistence Capable entity, or merely a Serializable at
different levels of OpenJPA type support.
[1] http://openjpa.apache.org/builds/latest/docs/manual/manual.html#type
[2] http://www.mail-archive.com/[email protected]/msg01370.html
> Mapping an unsupported type
> ---------------------------
>
> Key: OPENJPA-1612
> URL: https://issues.apache.org/jira/browse/OPENJPA-1612
> Project: OpenJPA
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.2.2, 2.0.0, 2.1.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Priority: Minor
> Fix For: 2.1.0
>
>
> As discussed on the dev mailing list [1]...
> I found that the following mapping:
> @Entity
> public class AnnoTest1 {
> @ManyToOne
> Object o;
> ...
> }
> This results in a warning message [2], but it is allowed. This JIRA will be
> used to detect this condition and fail fast.
> [1] http://openjpa.markmail.org/thread/6yphicehgclyobag
> [2] 297 TestConv WARN [main] openjpa.MetaData - OpenJPA cannot map field
> "test.AnnoTest1.o" efficiently. It is of an unsupported type. The field
> value will be serialized to a BLOB by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
