openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-293) OpenJPA should not require managed type enhancement
Date Tue, 24 Jul 2007 23:13:31 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Linskey updated OPENJPA-293:
------------------------------------

    Attachment: OPENJPA-293.patch

Patch to make enhancement optional. This feature is pretty experimental, but the only significant
code changes are to the enhancer. For enhanced classes, code pathways should remain virtually
unchanged.

Lazy loading in non-redefined types is currently not behaving correctly, and I have not yet
run the CTS in any configuration (including with enhancement) yet. 

To do:

- resolve issues marked with '#####' in patch
- lazy loading in field-access without redefinition
- clearing in pnew property-access without redefinition
- figure out how to auto-test the redefinition code, either in Java 5 or in Java 6
- test compound primary keys
- run CTS in the following combinations:
  * Java 6
  * Java 5 with javaagent
  * Java 5 without javaagent

> OpenJPA should not require managed type enhancement
> ---------------------------------------------------
>
>                 Key: OPENJPA-293
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-293
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: docs, kernel
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7
>            Reporter: Patrick Linskey
>             Fix For: 1.0.0
>
>         Attachments: OPENJPA-293.patch
>
>
> OpenJPA currently requires a post-compilation / deploy-time class processing step. This
should be made optional.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message