[RIVER-173] Entry spec does not say that an Entry class must be public

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: net_jini_core
• Bugtraq ID: 4283024
• Assignee: Unassigned
• Reporter: Phil Steitz
• Created: 02/Aug/07 01:36
• Updated: 02/Aug/07 01:38

Description

Bugtraq ID 4283024

The Entry spec never says anywhere that an Entry class must be public. It should. Actually, I think the requirements are stronger than that. At a minimum, every superclass that has usable (public, non-static, non-transient, non-final) declared fields must also be public. What's less clear to me is whether we should insist on all superclasses being public.The Entry spec never says anywhere that an Entry class must be public. It should. Actually, I think the requirements are stronger than that. At a minimum, every superclass that has usable (public, non-static, non-transient, non-final) declared fields must also be public. What's less clear to me is whether we should insist on all superclasses being public.