Hi Eoghan, I have not spent much time looking into this issue yet, but my
observation is that Service.getPort(java.lang.Class<T>
serviceEndpointInterface) does not return a usable proxy, this can be seen from
ServiceImplTest.testNonSpecificGetPort():
java.lang.AssertionError: expected:<bar> but was:<null>
at org.junit.Assert.fail(Assert.java:71)
at org.junit.Assert.failNotEquals(Assert.java:451)
at org.junit.Assert.assertEquals(Assert.java:99)
at org.junit.Assert.assertEquals(Assert.java:116)
at
org.apache.cxf.jaxws.ServiceImplTest.testNonSpecificGetPort(ServiceImplTest.java:82)
Is this because <jaxws:client> configuration not being applied to the proxy
properly, as you said?
Cheers,
Jervis
-----Original Message-----
From: Glynn, Eoghan [mailto:[EMAIL PROTECTED]
Sent: 2007?6?21? 16:09
To: [email protected]
Subject: RE: Picking up <jaxws:client> config from non-specific
Service.getPort()
Thanks Jervis,
Just to be clear, I think Service.getPort(java.lang.Class<T>
serviceEndpointInterface) does work, in the sense that it returns a
usable proxy.
What doesn't work is the injection of the configured <jaxws:client> bean
in this case.
Currently I'm working around the issue by programmatically setting the
required features on the proxy, but that's ugly to say the least.
So a fix for the injection issue would be great, as it would allow me to
revert to the normal spring-driven approach to enabling these features.
Cheers,
Eoghan
> -----Original Message-----
> From: Liu, Jervis [mailto:[EMAIL PROTECTED]
> Sent: 21 June 2007 04:01
> To: [email protected]
> Subject: RE: Picking up <jaxws:client> config from
> non-specific Service.getPort()
>
> Hi Guys, I can take a look into this issue. I plan to work on
> a relevant issue, which is Service.getPort(java.lang.Class<T>
> serviceEndpointInterface) does not work, JIRA CXF-735. I will
> make sure the injection stuff working properly when I work on cxf-735.
>
> Cheers,
> Jervis
>
> -----Original Message-----
> From: Dan Diephouse [mailto:[EMAIL PROTECTED]
> Sent: 2007?6?21? 1:33
> To: [email protected]
> Subject: Re: Picking up <jaxws:client> config from
> non-specific Service.getPort()
>
>
> I can take a peek... I just thought you wanted feedback on
> whether or not that was the right approach. Cheers,
> - Dan
>
> On 6/20/07, Glynn, Eoghan <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Dan,
> >
> > Obviously I misread your response ... i.e. I got the
> impression that
> > you intended to fix this, but it looks like the issue still
> exists ...
> > so I guess you meant that you weren't objecting to the
> problem being
> > fixed, as opposed to signing up to do the fix.
> >
> > Anyway, have you any ideas as to why the injection of the
> > <jaxws:client> bean doesn't occur if the port name isn't specified
> > explicitly by the application?
> >
> > /Eoghan
> >
> > > -----Original Message-----
> > > From: Dan Diephouse [mailto:[EMAIL PROTECTED]
> > > Sent: 01 May 2007 16:06
> > > To: [email protected]
> > > Subject: Re: Picking up <jaxws:client> config from non-specific
> > > Service.getPort()
> > >
> > > Hi Eoghan,
> > >
> > > +1 to fixing this like you said. I completely agree thats how
> > > it should
> > > work.
> > >
> > > - Dan
> > >
> > > On 5/1/07, Glynn, Eoghan <[EMAIL PROTECTED]> 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
> > >
> >
> > ----------------------------
> > IONA Technologies PLC (registered in Ireland) Registered Number:
> > 171387 Registered Address: The IONA Building, Shelbourne
> Road, Dublin
> > 4, Ireland
> >
>
>
>
> --
> Dan Diephouse
> Envoi Solutions
> http://envoisolutions.com | http://netzooid.com/blog
>
> ----------------------------
> IONA Technologies PLC (registered in Ireland) Registered
> Number: 171387 Registered Address: The IONA Building,
> Shelbourne Road, Dublin 4, Ireland
>
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
