[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 Unmarshalling-with-Commons-Annotations ) and separately, Aegis. My issue was that I could not unmarshall the response: <soap:Body> <LoginResponse xmlns="http://myexample.com";> <LoginResult> <id>9</id> <key>12345</key> </LoginResult> </LoginResponse> </soap:Body> To make this work, my Aegis mapping file for the service interface had to be: <mappings> <mapping namespace="http://myexample.com";> <method name="Login" action="http://myexample.com/Login";> <parameter index="0" mappedName="username" /> <parameter index="1" mappedName="password" /> <return-type name="LoginResult" /> </method> </mapping> </mappings> I also needed an Aegis mapping file for the object I needed to unmarshall, LoginResult: <mappings xmlns:ns1="http://myexample.com";> <mapping name="ns1:LoginResult"> <property name="id" mappedName="ns1:id" /> <property name="key" mappedName="ns1:key" /> </mapping> </mappings> The key thing in this file is that without the (dummy) prefix with the namespace on the mappings element, together with that repeated on all others, it just doesn't work. Looking at the response and comparing it to the LoginResult.aegis.xml, it kinda looks obvious, but search as I might, I could not get any documentation on this. Hope that helps the next person who tries to use Aegis mappings! Matt -- View this message in context: http://www.nabble.com/Unmarshalling-with-Aegis-tf3945884.html#a11193139 Sent from the XFire - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
