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 2008/05/31 20:31:44 UTC
[jira] Resolved: (RIVER-201) Show interfaces rather than classes in
browser's Matching Services pane.
[ https://issues.apache.org/jira/browse/RIVER-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Brouwer resolved RIVER-201.
--------------------------------
Resolution: Fixed
Fixed, compared to the patch attached the {{package.html}} file has been updated to reflect the new behavior.
> Show interfaces rather than classes in browser's Matching Services pane.
> ------------------------------------------------------------------------
>
> Key: RIVER-201
> URL: https://issues.apache.org/jira/browse/RIVER-201
> Project: River
> Issue Type: Improvement
> Components: com_sun_jini_example
> Affects Versions: jtsk_2.1
> Reporter: Bill Venners
> Assignee: Mark Brouwer
> Priority: Minor
> Fix For: AR2
>
> Attachments: RIVER-201.patch
>
>
> Bugtraq ID [6404689|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6404689]
> In the browser's Matching Services pane, an interface name is shown if the proxy only implements a single interesting interface, otherwise the proxy's class name is shown. It may be preferable in the latter case to display a list of interesting interface names instead, as the proxy class is seldom interesting to the user, and is especially uninteresting when it's a dynamic Proxy class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.