You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2007/08/02 03:38:53 UTC
[jira] Updated: (RIVER-173) Entry spec does not say that an Entry
class must be public
[ https://issues.apache.org/jira/browse/RIVER-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Steitz updated RIVER-173:
------------------------------
Description:
Bugtraq ID [4283024|http://bugs.sun.com/bugdatabase/view_bug.do?bug_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.
was:
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.
> 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]
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.