Error while invoking client...

Guys i'm using latest CXF to communicate with other side implemented using web menthods. This is the error i get when i inovke my test client on stubs generated by CXF. I'm new to this stack, so realy dont knwo wahts going on. Any pointers will be great help here... INE: Invoking handleMessage

Re: Error while invoking client...

Got it mate :) Ist an error on server side which is causing it. vashistvishal wrote: Guys i'm using latest CXF to communicate with other side implemented using web menthods. This is the error i get when i inovke my test client on stubs generated by CXF. I'm new to this stack, so realy

Additional element in Request Packet (SOAP payload ) is generated with name arg0

I'm consuming a service using CXF client which uses this wsdl mentioned below. When the outgoing message is sent it adds _arg0_ in soap packet, which is one element extra, client is not expecting this. soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; soap:Bodyns2:HelloWorld

Re: Aegis, Proxies Interfaces

Hi Dan, Cheers for letting me know. I've got a workaround in my code for now so I'll be waiting for the snapshot or the 2.0.2 release. Thanks for looking into it for me, Regards, Lee Dan Diephouse-2 wrote: Hi Lee, Looks like we got ourselves a bug. I've implemented a fix for this

RE: Obtaining source address and operation name

So it seems that we did some duplicate work in the code. In org.apache.cxf.transport.ChainInitiationObserver we already set most properties into the Exchange except the operation name, the operation name wont be available until the interceptor who knows how to parse the operation name info

Which maven module do i have to include?

Hi, i want to use cfx as a replacement for xfire. i have a schema-first approach with jaxb2 and i'm using maven 2 as build system. after a look at the cfx maven repository it is not obvious for me which module i have to include to have the right dependencies set up. Any suggestions? Many thx

Re: CXF Client not working

Hello, thanx. How could one access that fix? What version i shall put in dependencies? dkulp wrote: Just to let you know. I can reproduce this issue. I have a fix that I'm testing now and hope to have committed to SVN shortly. Dan On Friday 31 August 2007, exgorth wrote:

Different wsdl:port

Hi to all, I need to have a great number of clients pointing to some servers. The wsdl is the same for all services , except for the wsdl:port.../wsdl:port. The configuration of the clients/servers is stored in the database. Is possible to set a runtime the wsdl:port contents ? Otherwise how is

Re: Additional element in Request Packet (SOAP payload ) is generated with name arg0

Thanks Glen, This is what the binding looks like. It is doc/lit wrapped. It will be good if you can give me some pointers why it is adding _arg0_ in packet. -- wsdl:portType name=matt_HelloWorld3PortType wsdl:operation

Re: Additional element in Request Packet (SOAP payload ) is generated with name arg0

Looking at the schema, it looks like the CXF message is correct. The operation message points at the HelloWorld element: xsd:element name=HelloWorld type=tns:HelloWorld/ The HelloWorld type is a sequence with an arg0 element: xsd:complexType name='HelloWorld' xsd:sequence xsd:element

Re: Additional element in Request Packet (SOAP payload ) is generated with name arg0

Thanks Glen and Dan. If this the case (that arg0 is a correct arg in SOAP packet), then please point me how do i send the packet without this, becuse my intention is to send a warpper class which contains _id_ as a _string_. In this case that is HelloWorldReq. So in a nutshell i want to send

Re: Different wsdl:port

Hi For the Server side If you are using the JAXS API , you can Endpoint.publish() the service with different address. Object implementor1 = new AnonymousComplexTypeImpl(); String address = http://localhost:9000/anonymous_complex_typeSOAP;; Endpoint.publish(address, implementor1); If you are

Re: Setting the timeout on the client side

Hi CXF will load the cxf.xml as the default configuration file from the class path. If your configuration file's name is services.xml you need to specify it with java command line option -Dcxf.config.file=some_other_config.xml or load the configuration file with SpringBusFactory first.