0 Replies Latest reply on Apr 20, 2010 10:58 AM by mirapakai

    FLEX 3 - Question regarding namespace in Generated code for webservice



           I am kind of new to flex and have been learning it for past 20 days. Currently using FLEX builder 3 (with SDK 3.5) to generate webservice client wrappers and stuck for past several days with two problems in the soap request XML sent out from generated code.


      1. For operations with no arguments in my webservice. the generated xml has no operation name in soap body so it is not getting mapped to any operation(in red below)


                I am not sure if this a bug or a known issue or If I am missing some thing that is obvious... Any Ideas?

      2. For operations with Complex types as arguments in my webservice there comes a default namespace declaration as below(in red) which is conflicting with the namespace of the complex types and throwing deserialization errors because of validation against wrong namespace. If I remove that default namespace declaration and use the same xml message in some other soap client , it works fine.

                     <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SOAP-ENV:Body>.......


                  Is there a way in in FLEX through which I can avoid that default namespace declaration?


            Thanks a lot for reading with patience. Hope it was not too confusing.


           On a side note, I heard that there are some problems with webservice client code generated by FLEX builder. Is there any alternative approach in which I can use strongly typed object with out doing toomuch hand coding?