[JBoss JIRA] (JBWS-4003) [API] Add ClientConfigFeature(String configName) constructor
by Willem Salembier (JIRA)
[ https://issues.jboss.org/browse/JBWS-4003?page=com.atlassian.jira.plugin.... ]
Willem Salembier commented on JBWS-4003:
----------------------------------------
Any reason why the default {{configureProperties==false}} was chosen? The opposite seems to be the most used scenario.
> [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)
8 years, 4 months
[JBoss JIRA] (JBWS-4003) [API] Add ClientConfigFeature(String configName) constructor
by Willem Salembier (JIRA)
Willem Salembier created JBWS-4003:
--------------------------------------
Summary: [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)
8 years, 4 months