hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HTTPCLIENT-1770) [OSGi] metatype for org.apache.http.proxyconfigurator missing factoryPid
Date Thu, 22 Sep 2016 09:26:21 GMT

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

Julian Sedding updated HTTPCLIENT-1770:
    Attachment: HTTPCLIENT-1770-jsedding.patch

Attached patch fixes the issue.

> [OSGi] metatype for org.apache.http.proxyconfigurator missing factoryPid
> ------------------------------------------------------------------------
>                 Key: HTTPCLIENT-1770
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1770
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.2, 5.0 Alpha1
>            Reporter: Julian Sedding
>            Priority: Minor
>              Labels: osgi
>         Attachments: HTTPCLIENT-1770-jsedding.patch
> The metatype definition for {{org.apache.http.proxyconfigurator}} only lists the {{pid}}
attribute on the {{Designate}} element. As it is a {{ManagedServiceFactory}} supporting multiple
proxy configurations, the metatype should include a {{factoryPid}} attribute.
> E.g. in the Felix webconsole's configuration screen, there are currently two entries,
one for a singleton component configuration and one for a factory configuration. This is confusing
for users, especially since the singleton configuration does not work.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message