Does anyone know where this is headed to?? The current AR Systems capability or incapability rather to consume complex constructs limits a lot of what you can hope to do using web services. From hearsay, even version 8 does not have the ability to understand WSDL’s with complex constructs. Are there any definitive plans on when these would be reengineered to overcome these limitations?
>From my recent experience with attempting to consume complex WSDL’s, this >incapability appears to be more superficial, than internal to the AR Server. >It may be either at the Dev Studio level, or the actual WS plugin. It is >actually in some circumstances possible to bend these limitations which shows >that some of these limitations are not at the AR Server level itself. So that >makes me wonder if it could be incorporated with just be a patch enhancement >instead of planning it with a major release.. Also, does anyone know at what level is a WSDL interpreted when creating a Set Field filter action that uses a WSDL? Is it interpreted at the client level (dev studio) or server level (the WS plugin itself)??? What I mean to ask is when you enter the WSDL URI into the Set Fields action on a filter while creating a WSDL powered set fields filter, at what level does all the ‘magic’ happen? At the client side? Or on the server side?? I am trying to find if this is documented anywhere so if you have come across it please let me know where to look.. Cheers Joe _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
