13.07.2015 Views

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

Caché Upgrade Checklists - InterSystems Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Caché</strong> 2011.1 <strong>Upgrade</strong> Checklist3.2.11 Web Services Changes3.2.11.1 SOAP Fault HandlingIn this version, <strong>Caché</strong> now returns SOAP 1.1 faults with an HTTP status code of 400 for client errors, and 500 for servererrors as defined by WS-I Basic Profile. SOAP 1.2 faults already conformed to this use of 400 and 500 status codes. Furthermore,SOAP calls OnInternalFault for all %Status-based faults produced by the Initialize method. OnInternalFaultwas already being called for %Status based faults produced in other places in the code.If a client is expecting a status code of 200 for faults, then this will no longer work and the client application must bechanged.3.2.11.2 Wizard No Longer Generates SOAP HeadersThe SOAPHEADERS parameter will no longer be generated by the SOAP wizard. Instead the parameters XData block willbe used to specify which headers to expect at the method level based on the WSDL.Additional header information for a web service or web client is added in an XData block in the web service or web clientclass. The XData block has the parameters element in the configuration namespace as the root element.3.2.11.3 Maximum Method Name LengthIn this release, SOAP sets the length of method names to 180 characters. Some methods may end up with different nameswhen recreated by the SOAP wizard because truncation no longer needed.3.2.11.4 Do Not Close StreamsBeginning with this release, the files that implement the file streams used by SOAP web service and web client will not beclosed until the streams that use them are closed.3.2.12 BASIC And MVBASIC Changes3.2.12.1 Alterations To Line Continuation ProcessingBASIC and MV BASIC line continuation characters allow a source line to span multiple lines. Placing a line continuationcharacter as the last character on a line continues that statement on the next line. The BASIC line continuation character isan underscore (_); depending on the emulation options, MVBASIC can use either a vertical bar (|) or a backslash (\)as aline continuation character.Previous versions of BASIC and MVBASIC would sometimes allow a line continuation character to appear at places otherthan the last character of the line. However, this could cause problems if the line continuation character had an alternativeuse for another purpose. Beginning with this release, the continuation character must be the last character of the line.3.2.13 xDBC Changes3.2.13.1 Removal Of All Support For XAThis change removes some experimental XA code from the <strong>InterSystems</strong> JDBC driver. <strong>Caché</strong> does not support the XAprotocol, nor did the JDBC driver. However, as this was seriously considered a number of times, some experimental codewas added to test whether JDBC could fully support it one day. This feature was documented as unsupported, and <strong>InterSystems</strong>has now decided to remove this dead code as part of an overall Java cleanup.66 <strong>Caché</strong> <strong>Upgrade</strong> <strong>Checklists</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!