1) the endpoint interface - this is pretty much never going to work with
the simple frontend client without writing some custom subclass of
AbstractServiceConfiguration to map the arg0 names to the real names.
I wouldn't bother pursuing this one.
2) That error just means you specified the wrong qname for something.
The StartClient.java you sent has:
QName END_POINT_NAME = new
QName("http://service.webservice";, "ActServiceEndPoint");
However, the port name in the wsdl you sent is:
ActServicePortBinding
Dan
On Friday 14 December 2007, tcs wrote:
> I tried the 2.0.4 SNAPSHOT version with the SampleWebService server
> and client code that I sent to you.
>
> I replaced the older 'cxf-2.0.3-incubator.jar' in my web-service and
> web-service client classpath with the updated
> 'cxf-2.0.4-incubator-SNAPSHOT.jar'
>
> I deployed my webservice on tomcat. The behaviour is the same as the
> older version of CXF.
>
> I tested the client by building the ClientProxyFactoryBean using:
>
> 1) the endpoint interface
> The marshalled SOAP request contained the 'arg0' element which were
> not understood by the server. The server returned a fault.
>
> Exception in thread "main" org.apache.cxf.binding.soap.SoapFault:
> webservice.service.InvalidArgumentException: getActByPid(), method
> parameter 'theActPid' cannot be null
> at
> org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handl
>eMessage(Soap11FaultInInterceptor.java:70) at
> ...
>
> 2) the server WSDL url
> This exception is same as before.
>
> Exception in thread "main"
> org.apache.cxf.service.factory.ServiceConstructionException: Could not
> find portType named
> {http://service.webservice}ActServiceEndPointPortType at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.getInterfa
>ceInfo(ReflectionServiceFactoryBean.java:442) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initialize
>WSDLOperations(ReflectionServiceFactoryBean.java:450) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildServi
>ceFromWSDL(ReflectionServiceFactoryBean.java:274) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.initialize
>ServiceModel(ReflectionServiceFactoryBean.java:360) at
> org.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Ref
>lectionServiceFactoryBean.java:156) at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoin
>t(AbstractWSDLBasedEndpointFactory.java:74) at
> org.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.jav
>a:51) at
> org.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFacto
>ryBean.java:92) at
> client.StartClient.useServerWsdl(StartClient.java:74)
> at client.StartClient.main(StartClient.java:25)
>
> dkulp wrote:
> > I'm deploying a new 2.0.4 snapshot now that SHOULD fix it. (I'd
> > appreciate it if that could be verified) We'll probably shoot for
> > a 2.0.4 release mid January sometime.
> >
> > Dan
> >
> > On Thursday 13 December 2007, tcs wrote:
> >> Thanks very much for looking into this.
> >>
> >> I'm working on fixing this now, but it's definitely a fairly large
> >> change Any ideas as to when this will be working?
> >>
> >> Knowing when this feature would be available will be me plan my
> >> projects.
> >>
> >> thanks!
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727 C: 508-380-7194
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog
--
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog
