You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2011/04/08 19:08:05 UTC

[jira] [Resolved] (DISCOVERY-9) Documentation of other use cases

     [ https://issues.apache.org/jira/browse/DISCOVERY-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simone Tripodi resolved DISCOVERY-9.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.5
         Assignee: Simone Tripodi

Fixed on /trunk, see src/site/xdoc/best-practices.xml r1090352

> Documentation of other use cases
> --------------------------------
>
>                 Key: DISCOVERY-9
>                 URL: https://issues.apache.org/jira/browse/DISCOVERY-9
>             Project: Commons Discovery
>          Issue Type: Wish
>    Affects Versions: 0.4
>         Environment: all
>            Reporter: Ravi Luthra
>            Assignee: Simone Tripodi
>            Priority: Minor
>             Fix For: 0.5
>
>
> This is a request for more code samples. In particular I am having trouble finding code samples that let you find multiple implementations of a class, and instantiating them. What I am trying to do is populate a JTabbedPane with a bunch of Components that are found at runtime based on the jars in the classpath. The jars will have a META-INF/service folder with a file using the interface name (with package name). Right now I am easily able to load one class implementing this interface, but cannot seem to find the correct documentation for loading multiple class implementations of the interface. It seems this is one area that is missing.
> Another thing that would be cool is a general way to search a given package (in all jars) for classes that implement or extend a specific interface/class. This would remove the annoyance of creating service folder and other things. If that isn't in the scope of commons-discovery then never mind. I still think it would be bad-ass.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira