river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-173) Entry spec does not say that an Entry class must be public
Date Thu, 02 Aug 2007 01:36:53 GMT
Entry spec does not say that an Entry class must be public
----------------------------------------------------------

                 Key: RIVER-173
                 URL: https://issues.apache.org/jira/browse/RIVER-173
             Project: River
          Issue Type: Bug
          Components: net_jini_core
            Reporter: Phil Steitz
            Priority: Minor


Bugtraq ID [4283024|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4283024]

he 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.

-- 
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