A question about mutable attributes of type byte[]

Hi, A couple of weeks back, I was interested to follow the discussion about Calendar proxies and cloning. This got me to wondering, for persistent attributes of type "byte[]" which cannot be proxied, but are mutable, how does OpenJPA handle that case?

[jira] Commented: (OPENJPA-413) Fix some message text in the localizer.properties files

[ https://issues.apache.org/jira/browse/OPENJPA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537086 ] Albert Lee commented on OPENJPA-413: +++ openjpa-kernel/src/main/resources/org/apache/openjpa/kernel/localizer.

Re: [jira] Reopened: (OPENJPA-370) LoadFetchGroup annotation was not recognized during the fetch1

Hi Patrick, As I mentioned previously, there were two patches and patch1 was quick and dirty; whereas patch2 was more incline with the current architecture but has performance impact. The question is that why did we introduce the LoadFetchGroup concept at the beginning? With the fetch group itself

[jira] Commented: (OPENJPA-404) Backward-compatibility for pre-1.0 APIs

[ https://issues.apache.org/jira/browse/OPENJPA-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537047 ] Patrick Linskey commented on OPENJPA-404: - > It might inform this discussion to understand what BEA policy h

[jira] Updated: (OPENJPA-413) Fix some message text in the localizer.properties files

[ https://issues.apache.org/jira/browse/OPENJPA-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Teresa Kan updated OPENJPA-413: --- Attachment: OPENJPA-413.patch Attach the patch .. modified some messages for translation.. > Fix so

[jira] Created: (OPENJPA-413) Fix some message text in the localizer.properties files

Fix some message text in the localizer.properties files --- Key: OPENJPA-413 URL: https://issues.apache.org/jira/browse/OPENJPA-413 Project: OpenJPA Issue Type: Bug Affects Versions: 1.

Re: Proposal for releasing 1.0.1

Hi, Theoretically, this process should be a bunch easier now that we have an automated build machine running builds and uploading release candidates on the 1.0.x line. Currently, the 1.0.x build is passing the CTS and all our tests against Derby. A new release candidate build is automatically tri

[jira] Reopened: (OPENJPA-370) LoadFetchGroup annotation was not recognized during the fetch1

[ https://issues.apache.org/jira/browse/OPENJPA-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Linskey reopened OPENJPA-370: - It looks like this patch might have a performance impact due to the additional time require

Re: Proposal for releasing 1.0.1

Sounds good. -Patrick On 10/22/07, Albert Lee <[EMAIL PROTECTED]> wrote: > We have a need to freeze and build the current content of the 1.0.1 release. > > With Mike Dick's help and guidance, I am volunteering to do this release > work. > > I am wondering if the community has any objection to thi