Hi Craig, Thank you so much for this! much appreciated.
Craig Tataryn wrote: > > Hi mdaoud, I'll try and whip something up today. > > Craig. > > On 2011-07-20, at 10:43 AM, mdaoud wrote: > >> >> Hi craig, >> >> Is there any update regarding the document? >> >> Thanks, >> >> >> Craig Tataryn wrote: >>> >>> I'll try to get you some documentation on how I handled this all within >>> Spring. But it will have to wait until next week I'm afraid. >>> >>> Craig. >>> >>> On 2011-07-14, at 10:45 AM, mdaoud wrote: >>> >>>> >>>> Actually it will be a bit manual nightmare because my requests naming >>>> like >>>> updateCustomerRequest, deleteAddressRequest and those need to be >>>> unmarshalled to Address class and Customer class!! >>>> >>>> I still can have a look and try doing it. Is there any documentation >>>> for >>>> how >>>> to override the setRootElement? >>>> >>>> >>>> >>>> Craig Tataryn wrote: >>>>> >>>>> >>>>> >>>>> On 2011-07-14, at 10:16 AM, mdaoud <[email protected]> wrote: >>>>> >>>>>> >>>>>> Thank you Craig for this explanation. Unfortunatelly, yea the >>>>>> xxxxSOAPRequest >>>>>> is my main root in the SOAP:BODY!!! >>>>>> and yea i am using Spring OXM. >>>>>> >>>>> >>>>> That's a good thing then if it's your root element, it means >>>>> setRootElement will work in your case. >>>>> >>>>> You just need a way of automatically determining the xxxx part on a >>>>> per >>>>> request basis (ie. Perhaps based on the service name requested?) >>>>> >>>>> Craig >>>>> >>>>> >>>>>> That makes me wonder how other applications handle this issue? I have >>>>>> over >>>>>> 100 requests and i would like to (un)marshal the requests/responses >>>>>> in >>>>>> a >>>>>> simple way (instead of keep parsing with XPath or JDom) >>>>>> >>>>>> any suggestions? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/Unmarshalling-multiple-xml-to-one-class-tp32059761p32062059.html >>>>>> Sent from the Castor - User mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe from this list, please visit: >>>>>> >>>>>> http://xircles.codehaus.org/manage_email >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe from this list, please visit: >>>>> >>>>> http://xircles.codehaus.org/manage_email >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Unmarshalling-multiple-xml-to-one-class-tp32059761p32062258.html >>>> Sent from the Castor - User mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe from this list, please visit: >>> >>> http://xircles.codehaus.org/manage_email >>> >>> >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/Unmarshalling-multiple-xml-to-one-class-tp32059761p32100369.html >> Sent from the Castor - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://old.nabble.com/Unmarshalling-multiple-xml-to-one-class-tp32059761p32100412.html Sent from the Castor - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
