[jbossws-issues] [JBoss JIRA] (JBWS-3836) Convention for automatic predefined client/endpoint configuration retrieval

[Alessio Soldano (JIRA)]

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

Alessio Soldano updated JBWS-3836:
----------------------------------
    Fix Version/s: jbossws-cxf-5.0.0.Beta2
                       (was: jbossws-cxf-5.0)


> Convention for automatic predefined client/endpoint configuration retrieval
> ---------------------------------------------------------------------------
>
>                 Key: JBWS-3836
>                 URL: https://issues.jboss.org/browse/JBWS-3836
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>          Components: jbossws-cxf, jbossws-integration, productivity
>            Reporter: Alessio Soldano
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-5.0.0.Beta2
>
>
> "An alternative idea would be to provide a convention for automatically 
> reading a pre-defined client configuration, for instance based on the 
> SEI class FQN. So for instance, we could say that for a port retrieved 
> as follows
> import org.foo.ServiceIface;
> ...
> Service service = Service.create(new URL("...?wsdl"), serviceQName);
> ServiceIface port = (ServiceIface)service.getPort(portQName, 
> ServiceIface.class);
> instead of directly going and fetching the 
> "Standard-Client-Configuration" from the container webservices 
> management model we'd first try getting a configuration named 
> "org.foo.ServiceIface" (still in the webservices model) and only 
> fallback to the "Standard-Client-Configuration" if that's not found.
> That would allow for different configurations to clients without 
> touching their code; the only requirement is the clients run in-container."
> http://lists.jboss.org/pipermail/jbossws-dev/2014-September/002211.html



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)