1# 2# ReleaseNotes.txt 3# 4 5The following is a compilation of various issues developers should be aware of 6when developing Web services using SOAP::Lite. 7 8LIMITED WSDL SUPPORT - SOAP::Lite is not capable of generating WSDLs 9automatically. If you require a WSDL for a service written using SOAP::Lite, 10please consider using a tool like XML Spy, or CapeClear's WSDL Editor. 11 12NO ENTITY DECODING 13SOAP::Lite uses XML::Parser::Lite which relies on Unicode support in Perl and 14doesn't perform XML ENTITY decoding. 15 16LIMITED SUPPORT FOR MUSTUNDERSTAND and ACTOR ATTRIBUTES 17SOAP::Lite does not currently heed the soap:mustUnderstand XML attribute, or 18SOAP actor attributes. 19 20DOCUMENT-LITERAL SUPPORT 21All literal encoding support for SOAP::Lite is marked EXPERIMENTAL, and it is 22incomplete. Developers are encouraged to use this capability but should be 23fore-warned. 24As an alternative, SOAP::WSDL or XML::Compiled::SOAP may be used for 25document/literal bindings derived from WSDL definitions. 26 27CLIENT SIDE WSDL SUPPORT 28SOAP::Lites ability to consume a WSDL and generate the necessary message based 29on that WSDL is improving, but it does not work with complex types. 30As an alternative, SOAP::WSDL or XML::Compiled::SOAP may be used for 31document/literal bindings derived from WSDL definitions. 32 33SERVICE SIDE WSDL SUPPORT 34Perl is a loosely typed language making it extraordinarily difficult to generate 35a reliable WSDL based upon reflection of somekind. Therefore, no WSDL can be 36generated using SOAP::Lite. 37 38SOAP FAULT NOT GETTING SERIALIZED PROPERLY 39A user reported that when a service run under Perl version 5.5003 issues the 40die command with a SOAP::Fault as input, that SOAP::Lite does not properly 41serialize the Fault object. However, the same code works under 5.6 and above. 42 43NULL BODIES 44SOAP::Lite currently allows users to construct an Envelope using a null body, 45e.g. <Envelope><Body /></Envelope>. However, SOAP::Lite services have no way 46of processing such a message. 47 48XML NAMESPACES ABSENT FROM RESPONSES 49A user reported that under mod_perl for a series of requests which were using 50SOAP 1.1 and 1.2, that some of the responses to incoming messages lacked the 51XSD and XSI namespace declarations causing an error with the receiving .NET 52client for those response lacking these attributes. 53 54OBJECTS BY REFERENCE 55SOAP::Server->objects_by_reference is marked EXPERIMENTAL 56 57