[
https://issues.apache.org/jira/browse/OPENJPA-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14607963#comment-14607963
]
ASF subversion and git services commented on OPENJPA-2600:
--
[
https://issues.apache.org/jira/browse/OPENJPA-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved OPENJPA-2600.
Resolution: Fixed
finally removed the 2 mentioned classes.
finally remove
[
https://issues.apache.org/jira/browse/OPENJPA-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608439#comment-14608439
]
Mark Struberg commented on OPENJPA-2341:
While tinkering a unit test I came
[
https://issues.apache.org/jira/browse/OPENJPA-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14608457#comment-14608457
]
Mark Struberg commented on OPENJPA-2341:
The missing field handling is btw also
Not quite sure about this. I don’t like it as Persistent is an openjpa
annotation. Probably use PERS if @Basic or @Column is specified and the type is
_not_ Serializable?
In 2.2 the spec only explicitly requires the support of Serializable. So from a
spec pov it is fine, but it is still
Hi folks!
I sense some chicken-egg proglem with FieldMapping and what field becomes a
persistent column.
The point is that only fields which have a valid FieldMapping will become a
persistent column.
Currently the main check - as far as I do understand so far - is in
Hi Mark,
didnt check the code but wonder if adding @Persistent solves it, if so we
can just implicitely consider a field @Persistent if there are some other
annotations (would be the same with @Externalizer/@Factory I think)
Romain Manni-Bucau
@rmannibucau https://twitter.com/rmannibucau |
Any more context as to the problem you're running into/trying to solve?
On Tue, Jun 30, 2015 at 11:31 AM, Mark Struberg strub...@yahoo.de wrote:
Hi folks!
I sense some chicken-egg proglem with FieldMapping and what field becomes
a persistent column.
The point is that only fields which have
Hi Rick!
I’m trying to finally solve the long outstanding issue that our @Strategy and
FieldStrategies configuration is pretty much broken. See
https://issues.apache.org/jira/browse/OPENJPA-2341
It is broken if the type you like to store is not Serializable. E.g. (taken
from my current unit
[
https://issues.apache.org/jira/browse/OPENJPA-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OPENJPA-2341:
---
Attachment: OPENJPA-2341-wip-1.patch
work in progress; these tests fail as the mapped field
10 matches
Mail list logo
