[jbossws-issues] [JBoss JIRA] (JBWS-4003) [API] Add ClientConfigFeature(String configName) constructor

[Alessio Soldano (JIRA)]

    [ https://issues.jboss.org/browse/JBWS-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292331#comment-13292331 ] 

Alessio Soldano commented on JBWS-4003:
---------------------------------------

AFAIR, the reason why default configureProperties = false is that in the past not all implementations of ClientConfigurer supported properties setup.
As for adding the additional constructor in ClientConfigFeature, I'd be fine with it but doing this(null, configName, false), that is with configureProperties = false, otherwise we'd have 2 different default behaviors (and at the same time I don't want to change the constructror with 2 parameters).
A change in default behaviour would likely need a major API release, which is not really on the radar now...

> [API] Add ClientConfigFeature(String configName) constructor
> ------------------------------------------------------------
>
>                 Key: JBWS-4003
>                 URL: https://issues.jboss.org/browse/JBWS-4003
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>            Reporter: Willem Salembier
>
> For predefined {{client-config}} settings in {{standalone.xml}}, it would be more elegant to add a new constructor in {{org.jboss.ws.api.configuration.ClientConfigFeature}} that only takes a configName and forces {{configureProperties=true}}.
> {code}
>    public ClientConfigFeature(String configName) {
>       this(null, configName, true);
>    }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)