0 Replies Latest reply on Feb 1, 2007 5:36 AM by idpjc

    web service request population


      As the <mx:request> structure seems to be the place to specify all the web service elements, can anyone please tell me how this would work where we could have the situation of optional data?

      For example if there was a web service which accepted a number of previous addresses (say 3) but you only had 2 addresses, what would the <mx:request> structure contain (i.e. would you have to specify the elements three times but leave the the last set of elements with no data ( in this case would the flex soap message generation automatically leave out the last address elements as there is no data, otherwise we could have an issue if the web service receives a empty [blank] address?).

      If anyone has a code example of this situation that would also be appreciated