You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Mark Brouwer (JIRA)" <ji...@apache.org> on 2007/07/24 09:51:31 UTC
[jira] Updated: (RIVER-29) Make some of the private fields of
MarshalledInstance protected for the purpose of access by subclasses
[ https://issues.apache.org/jira/browse/RIVER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer updated RIVER-29:
------------------------------
Component/s: net_jini_io
Affects Version/s: jtsk_2.1
> Make some of the private fields of MarshalledInstance protected for the purpose of access by subclasses
> -------------------------------------------------------------------------------------------------------
>
> Key: RIVER-29
> URL: https://issues.apache.org/jira/browse/RIVER-29
> Project: River
> Issue Type: Wish
> Components: net_jini_io
> Affects Versions: jtsk_2.1
> Reporter: Mark Brouwer
> Priority: Minor
>
> {{net.jini.io.MarshalledInstance}} allows for subclassing but some of the fields that might be needed by a subclass can't be accessed as they are declared {{private}}. A subclass has to pass these in to the constructor of the superclass so must have 'access' to them. There seems to be no harm to make them {{protected}}, especially since they are {{final}}. See also this posting on the [river-dev|http://mail-archives.apache.org/mod_mbox/incubator-river-dev/200706.mbox/%3c46652236.7070005@cheiron.org%3e] mailing list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.