cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <...@envoisolutions.com>
Subject Re: Picking up <jaxws:client> config from non-specific Service.getPort()
Date Tue, 01 May 2007 15:06:21 GMT
Hi Eoghan,

+1 to fixing this like you said. I completely agree thats how it should
work.

- Dan

On 5/1/07, Glynn, Eoghan <eoghan.glynn@iona.com> wrote:
>
>
>
> Folks,
>
> After an amount of head-banging-on-desk, I noticed that the
> <jaxws:client> config isn't picked up via the non-specific
> Service.getPort(), even when the actual port selected matches the bean
> ID of the configured <jaxws:client>.
>
> By the non-specific Service.getPort(), I mean the form of this API where
> a specific port name is not provided explicitly by the app, instead the
> Service impl handles the selection of an appropriate port.
>
> This is easily seen by removing the @Ignore from the
> ServiceImplTest.testNonSpecificGetPort() unit test that I just
> committed.
>
> This should this work, right? I mean, what does it matter if endpoint is
> selected by the Service impl or specified explicitly by the app, either
> way a matching <jaxws:client> bean should be wired in, or?
>
> Cheers,
> Eoghan
>
>


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

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