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

[Alessio Soldano (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-3011:
----------------------------------

         Assignee: Alessio Soldano
    Fix Version/s: jbossws-cxf-4.0.1
                   jbossws-native-4.0.1
      Component/s: jbossws-cxf


I've added the jbossws-cxf component to this jira and assigned to me to reconsider this now that the endpoint configuration is part of AS 7 domain with JBossWS 4.
                
> Make the default JAX-WS Client and Endpoint Configuration configurable
> ----------------------------------------------------------------------
>
>                 Key: JBWS-3011
>                 URL: https://issues.jboss.org/browse/JBWS-3011
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-cxf, jbossws-native
>    Affects Versions: jbossws-native-3.3.0.CR2
>            Reporter: david.boeren
>            Assignee: Alessio Soldano
>            Priority: Minor
>             Fix For: jbossws-cxf-4.0.1, jbossws-native-4.0.1
>
>
> 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, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira