Re: [xfire-user] SoapAction

Hi, I've been battling to try and get Aegis to generate the SOAPaction in the HTML header as I'm communicating with a .NET WS which won't accept an empty SOAPaction . In my mappings, I've got: method name=Login action=Login mappedName=Login and in my client I've got:

[xfire-user] RE: Anyone have success with common-annotations

It sounds like you have not run the ant task to compile the necessary extra java file. When you run this, you will get a derived java file, which will need to be compiled. The name of this file will be something like IHelloWorld$_attributeRepository.java. It will not work by including the

[xfire-user] Unmarshalling with Commons Annotations

I have a client set up which calls an external WS. The body of the SOAP response I get is: soap:Body LoginResponse xmlns=http://myexample.com; LoginResult id9/id key12345/key /LoginResult

Re: [xfire-user] SoapAction

.html). Any help would be appreciated, as I really want to continue using xfire, but have to use Java 1.4. MattJax wrote: When I try that, I get: java.lang.NoSuchMethodError: java.lang.Integer.valueOf(I)Ljava/lang/Integer; at org.codehaus.xfire.aegis.AegisServiceConfiguration

Re: [xfire-user] SoapAction

I'd much rather use the AegisServiceConfiguration to achieve this. A snapshot would be great. Tomek Sztelak wrote: You can setup SOAPAction using outHandlers (as i know some ppl do it so it works). I will also fix this problem with AegisServiceConfiguration ASAP and if you want i can

Re: [xfire-user] SoapAction

Well spotted! However, I have just tried this and it still does not affect the SOAPAction in the HTTP request. BTW the xsd (http://xfire.codehaus.org/schemas/1.0/mapping.xsd) for the Aegis mappings only seems to include property elements as children of the mapping element. Is there an updated

Re: [xfire-user] aegis binding XML Schema

Is the latest Aegis mapping schema document published somewhere? The latest version I can find (http://xfire.codehaus.org/schemas/1.0/mapping.xsd) does not include the method element and so I am not sure of the allowed syntax with xfire 1.2.6. Cheers, Matt Dan Diephouse wrote: Hi Nicolas,

Re: [xfire-user] SoapAction

With major credits to: http://jira.codehaus.org/browse/XFIRE-490, have managed to get the SOAP action set in a workaround way. First created the handler class, which accepts the action I want then, once I've created my service, I add the following line to get the SOAPAction in the HTTP header:

Re: [xfire-user] SoapAction

Ankur Shah wrote: the link doesn't work BTW I think it does! It's not hyperlinked though... Ankur Shah wrote: More than likely the action is going to be same as method/operation name. If you want to use the operation name dynamically using this method, then you'll need to do 2 things: 1)

Re: [xfire-user] SoapAction

Snapshot working fine with regards adding the SOAPAction to the HTTP header. Need to use: factory.getServiceConfigurations().add(0, conf); not factory.getServiceConfigurations().add(conf); and the aegis.xml file needs: method name=Login action=Login not method name=Login

Re: [xfire-user] Unmarshalling with Commons Annotations

Thanks Tomek. I shall stop using Commons Annotations straight away then! I've got the SOAPAction to work using your latest snapshot and Aegis. However, I can't get the response to populate my return object. As before the response I get back is: soap:Body LoginResponse

Re: [xfire-user] Xfire SOAP Client and complex type parameter

There are a number of ways of doing this, but all involve some kind of binding. http://xfire.codehaus.org/Bindings is a good place to start. If you are using Java 5, I'd recommend Java 5 annotations, http://xfire.codehaus.org/JSR+181+Annotations. The classes can be generated from the WSDL as

Re: [xfire-user] Xfire SOAP Client and complex type parameter

Maybe you could give an example of the WS call you are trying to make? Erik Allais wrote: hi Matt, i dont really touch the XFire implementation of the server I generate Xfire Web service with Mule ESB i write my own SOAP client with Xfire but Complex Type parameter is hard

Re: [xfire-user] Xfire SOAP Client and complex type parameter

=xsd:string/ xsd:element name=password type=xsd:string/ xsd:element name=version type=xsd:string/ /xsd:all /xsd:complexType i need make this complex type with a java object but how exactly? MattJax wrote: Maybe you could give an example of the WS call you are trying to make

[xfire-user] Unmarshalling with Aegis

This is a posting for information only. I've had loads of trouble trying to unmarshall SOAP responses using commons annotations ( http://www.nabble.com/Unmarshalling-with-Commons-Annotations-tf3871884.html Unmarshalling-with-Commons-Annotations ) and separately, Aegis. My issue was that I could

Re: [xfire-user] Unmarshalling with Aegis

[apologies for first unreadable post - I clicked 'Message is in HTML format' by mistake!] This is a posting for information only. I've had loads of trouble trying to unmarshall SOAP responses using commons annotations ( http://www.nabble.com/Unmarshalling-with-Commons-Annotations-tf3871884.html

Re: [xfire-user] Unmarshalling with Aegis

If you look at BookService.aegis.xml in the example (in the examples/book directory that ships with the distribution) you can see: mappings xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://xfire.codehaus.org/schemas/1.0/mapping.xsd; mapping method

[xfire-user] Namespace declared in body element in 1.2.6

Hi, I've got a client application which is using Java 5 and XFire 1.2.4 and Annotations to call a web service. When upgrading to XFire 1.2.6, I'm seeing different behaviour in that the namespace and prefix declaration is now split between being specified on the body element as well as the

[xfire-user] Aegis problems migrating from xfire

Hi I am migrating a project from xfire-1.2.6 to CXF 2.1.1 and JDK1.5.0_15. I cannot get the CXF client code to use my aegis mappings at all. I've tried a number of different ways to generate my client as follows: My interface for the Web Service is: public interface IPartners {

Re: [xfire-user] Aegis problems migrating from xfire

Apologies! I have posted this on the wrong mailing list. Matt -- View this message in context: http://www.nabble.com/Aegis-problems-migrating-from-xfire-tp18757019p18757064.html Sent from the XFire - User mailing list archive at Nabble.com.