cxf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Client & Endpoint Config [was Re: Generic client config]
Date Wed, 11 Apr 2007 18:53:44 GMT
On 4/11/07, Dan Diephouse <dan@envoisolutions.com> wrote:
>
> Hiya
>
> On 4/11/07, Glynn, Eoghan <eoghan.glynn@iona.com> wrote:
>
> >
> > 1. How does the <jaxws:client> id attribute relate to the target port
> > name? e.g. id="MyPort", or id="MyService/MyPort", or
> > id="{http://myNamespace}MyService/MyPort ", or some wildcarded variant,
> > or something else entirely?
>
>
> It pulls out the <jaxws:client> config by the port name.
>
> From the ServiceImplTest/soapServiceConfig.xml:
>
>   <jaxws:client id="{ http://apache.org/hello_world_soap_http}SoapPort<http://apache.org/hello_world_soap_http%7DSoapPort>"
> abstract="true">
>      <jaxws:properties>
>       <entry key="foo" value="bar"/>
>     </jaxws:properties>
>   </jaxws:client>
>


I'm just thinking through this some more...

I think this is liable not to work if we have both an <endpoint> and
<client> defined in the same context as Spring will create the same ids for
them. Therefore when we do configureObject() its liable to get confused and
not work.

What do people think of requiring that people add ".client" or ".endpoint"
to the ids? Maybe I'm missing something, but that might be the only way to
get this to work.

- Dan

-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message