- 
    Bug 
- 
    Resolution: Won't Fix
- 
     P3 P3
- 
    None
- 
    6
- 
    None
- 
        generic
- 
        generic
                    Scott Violet wrote:
I think we should consider putting the code that dug out fields back :(
The important thing is none of our public API relies on it, so that you can persist any public classes in a sandbox without reflection hacks. Developers that want to use LTP to persist private fields, should be allowed to, assuming they have the right permissions.
Shannon Hickey wrote:
What do you think about reverting part of your change for compatibility reasons? That is, favor field access if you have the right permissions, otherwise use getters.
            
I think we should consider putting the code that dug out fields back :(
The important thing is none of our public API relies on it, so that you can persist any public classes in a sandbox without reflection hacks. Developers that want to use LTP to persist private fields, should be allowed to, assuming they have the right permissions.
Shannon Hickey wrote:
What do you think about reverting part of your change for compatibility reasons? That is, favor field access if you have the right permissions, otherwise use getters.
- relates to
- 
                    JDK-6412286 DOC: LTP: Unspecified NPE in java.beans.DefaultPersistenceDelegate.instantiate method -           
- Resolved
 
-         
- 
                    JDK-4741757 LTP: XMLEncoder ignores persistence delegates when used with java web start -           
- Resolved
 
-