[jbossws-issues] [JBoss JIRA] Commented: (JBWS-3011) Make the default JAX-WS Client and Endpoint Configuration configurable

[Darran Lofthouse (JIRA)]

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

Darran Lofthouse commented on JBWS-3011:
----------------------------------------

If a change is required that will affect all clients or all endpoint why not just edit the "Standard Client" or "Standard Endpoint" definitions directly?  

Why does a new configuration need to be added then a system property set to specify the new configuration is the new default leaving the existing defaults unused.


> Make the default JAX-WS Client and Endpoint Configuration configurable
> ----------------------------------------------------------------------
>
>                 Key: JBWS-3011
>                 URL: https://jira.jboss.org/jira/browse/JBWS-3011
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-native
>    Affects Versions: jbossws-native-3.3.0.CR2
>            Reporter: David Boeren
>            Priority: Minor
>
> I would like to have a possibility to configure the default JAX-WS Client and Endpoint Configuration. Currently the "Standard Client" (in file "standard-jaxws-client-config.xml") and "Standard Endpoint" (in file "standard-jaxws-endpoint-config.xml") are hardcoded in the interface org.jboss.ws.metadata.config.ConfigurationProvider as default configurations.
> If a common enterprise specific configuration is in available then it would be nice to have the possibility to set it by default. Currently, every endpoint or client must define the annotation @EndpointConfig and @HandlerChain respectively.
> A possibility would be to have two system properties to define the default configuration name for clients and endpoints for a JBoss server.  I think from a JBoss/JBossWS perspective it makes sense to name them something like jbossws.jaxws.default.endpoint.config and jbossws.jaxws.default.client.config
> By-the-way: It probably make also sense to make the default  configuration filename configurable. The filename is more or less at the same place in the code. The solution could look similar as described for configuration name. However, configurable default filenames is not a requirement for me.
> As a test, I have patched three classes in my JBoss in order to have a possibility to set the default configuration by system property.
> For client configuration:
> - org.jboss.ws.metadata.umdm.ClientEndpointMetaData
> - org.jboss.ws.tools.metadata.ToolsEndpointMetaData
> For endpoint configuration:
> - org.jboss.ws.metadata.umdm.ServerEndpointMetaData
> For example, I have only replaced the line
> String configName = ConfigurationProvider.DEFAULT_ENDPOINT_CONFIG_NAME;
> with the following
> String configName = System.getProperty("jbossws.jaxws.default.endpoint.config", "AXA Standard Endpoint");

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira