River
  1. River
  2. RIVER-173

Entry spec does not say that an Entry class must be public

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: net_jini_core
    • Labels:
      None
    • Bugtraq ID:
      4283024

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Phil Steitz
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development