> -----Original Message----- > From: Dan Diephouse [mailto:[EMAIL PROTECTED] > Sent: 21 June 2007 05:00 > To: [email protected] > Subject: Re: Picking up <jaxws:client> config from > non-specific Service.getPort() > > Hiya Jervis, > > I was looking into this issue for a while tonight, but I > haven't figured it out really. I do know that the first > problem is that the "{...}SoapPort" > isn't the one being selected by the getPort() call - its > selecting the GreeterPort. But even if I change my config its > not being picked up. But I could be doing something silly, so > you might want to verify that for yourself :-)
I can confirm that as I also noticed the SoapPort versus GreeterPort mismatch when I came across this issue first, and also found that that changing the bean id to "...GreeterPort" had no effect. Cheers, Eoghan > > Cheers, > - Dan > > On 6/20/07, Liu, Jervis <[EMAIL PROTECTED]> wrote: > > > > 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 > > > > > > -- > 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
