Task #198 (new)
Opened 18 years ago
Last modified 17 years ago
ShallowCopy should not use reflection.
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | minor | Milestone: | Unscheduled |
Component: | General | Version: | 3.0-M2 |
Keywords: | cleanup, reflection, java5 | Cc: | |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
Currently for weird javassist/hibernate/jboss reasons, we weren't able to use code generation to create new instances for ome.util.Filterable instances (Filterable.newInstance()). And instead we are using Java reflection to create new instances.
Perhaps these Java5-related issues will go away with later take-up. In any even a reworking of ShallowCopy? (#194) needs to be examined.
Change History (2)
comment:1 Changed 18 years ago by jmoore
- Milestone changed from Unscheduled to 3.0-M4
comment:2 Changed 17 years ago by jmoore
- Milestone changed from 3.0-Beta2 to Unscheduled
Rescheduling with #334.