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 xmlns="http://myexample.com";> <LoginResult> <id>9</id> <key>12345</key> </LoginResult> </LoginResponse> </soap:Body> My mapping file for the service interface is: <mappings> <mapping> <method name="Login" action="http://myexample.com/Login"; namespace="http://myexample.com";> <parameter index="0" mappedName="username"/> <parameter index="1" mappedName="password"/> <return-type mappedName="LoginResult" componentType="com.optimad.imd.ws.LoginResult"/> </method> </mapping> </mappings> I have tried this with and without an Aegis mapping file for my return object com.optimad.imd.ws.LoginResult, but cannot get this to unmarshall. Any clues or pointers to the area of the x-fire code where I should look? Thanks in advance, Matt Tomek Sztelak wrote: > > Being honest you are probably first person ,i know of, who uses > commons annotations :). So can't help much here. But you can setup > SOAPAction via aegis mapping files ( i tested it few day ago). To make > it work you just need to use latest snapshot , not last stable (1.2.6) -- View this message in context: http://www.nabble.com/Unmarshalling-with-Commons-Annotations-tf3871884.html#a11117916 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
