Posted by a customer on 15/03/2011
I note that, when I create a Web Service Resource by importing a WSDL based on an Ebase Integration Service, each of the imported fields has the 'empty field' behaviour set to 'write empty element' by default. This causes problems for field types other than char, as Ebase's web service engine cannot interpret (for example) an empty date format field and throws an error.
Please could this behaviour be reviewed, either with a view towards making the default empty field action configurable (so I could opt for 'omit element' as my default to be used throughout) or to make the configuration respectful of the status of the field being imported (e.g. to use 'omit element' for non-mandatory fields and 'write empty element' for mandatory fields, or to use 'omit element' for fields whose data type does not permit an empty element to be accepted such as dates).
Option to configure 'write empty element' in Web Services
Moderators: Jon, Steve, Ian, Dave
-
- Moderator
- Posts: 184
- Joined: Tue Sep 11, 2007 8:58 am
Who is online
Users browsing this forum: No registered users and 38 guests