[ https://issues.apache.org/jira/browse/OPENJPA-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Heath Thomann resolved OPENJPA-1854. ------------------------------------ Resolution: Not A Problem Fix Version/s: (was: 2.1.2) (was: 2.0.2) (was: 1.2.3) > A 'find' or 'query' may return multiple instances of Entities which contain > Embeddables, where the Embeddables use String identities, if the id value has > trailing spaces. > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: OPENJPA-1854 > URL: https://issues.apache.org/jira/browse/OPENJPA-1854 > Project: OpenJPA > Issue Type: Bug > Components: kernel > Affects Versions: 1.2.2, 1.3.0, 2.0.0 > Reporter: Heath Thomann > Assignee: Heath Thomann > Attachments: OPENJPA-1854-1.2.x.test > > > This issue is very similar to that of OPENJPA-1501, with one twist.......I've > found that when you have an Embeddable, which has Strings as the keys/ids, > openJPA code puts the Embeddable into an ObjectID by design, rather than a > StringID....recall, the fix to OJ1501 was to strip white space from the end > of a user's String key when that String was placed into a StringID. So, the > strings in an Embeddable would also need to be stripped, just as was done in > OJ-1501, but unfortunately it would seem to be harder to do so for > Embeddables since openJPA code doesn't necessarily know what types are > contained in the Embed. > I've created a JUnit test case which has three test methods. The test is > attached here. -- This message was sent by Atlassian JIRA (v6.1.4#6159)