IBM-SOAP Changes Record

This file lists the changes from version to version. The most recent version is at the top.

• Version 1.2:
  • New features:
    • Added support for 1-dimensional arrays using SOAP encoding style.
    • Added ability to author services in scripting languages; scripts can be authored in any BSF-supported scripting language.
    • Added a service manager client. No longer required to use html UI to manage (deploy/query/undeploy/list) services. See com.ibm.soap.server.ServiceManagerClient.
    • Added a calculator demo. The server side is authored in JavaScript. All calculations are performed remotely via SOAP calls. Client side is a Java UI.
    • Added support for a literal XML encoding style (http://www.ibm.com/namespaces/ibm-soap/literalxml). A serializer/deserializer is pre-registered for RPC parameters. The pre-registered serializer/deserializer supports serializing/deserializing parameters of type org.w3c.dom.Element.
    • Added a new client to the addressbook demo: demos.addressbook.GetAllListings. This client will retrieve all the listings in the addressbook and print them to standard out. The service that this client invokes returns the listings using the new literal XML encoding style.
    • Added a new client to the addressbook demo: demos.addressbook.PutListings. This client will read an XML file on the client containing address listings, and send them to a service which will populate the addressbook with them. A sample file of listings is included: /demos/addressbook/sample_listings.xml.
  • Changes:
    • Improved "No Signature Match" error message from ReflectionUtils; the class names of array types are now correctly displayed.
    • Made namespaceURI and localPart properties of QName writeable; they were previously read-only.
    • Improved error handling of the primitive serializer/deserializer defined in SOAPMappingRegistry.
    • Improved flow of ParameterSerializer; some of the common functionality was factored out and put into SoapEncUtils.
    • DeploymentDescriptor.buildSOAPMappingRegistry(...) now allows the JavaType argument to be null.
    • Changed SOAPMappingRegistry to use reflection to pre-register XMI-related serialization/deserialization components only if the classes can be loaded.
  • Bug fixes:
    • In SOAPMappingRegistry, the primitive deserializer had intQName where there should have been byteQName and shortQName; it was a copy-and-paste error.
    • SOAPHTTPConnection.send(...) now returns the HTTP headers contained in the response.
    • The apiDocs somehow didn't find their way into the v1.1 distribution.

• Version 1.1:
  • New features:
    • Completed implementation of SMTP transport.
    • Now handles serialization/deserialization of top-level nulls in XMI (nulls are special-cased, similar to java.lang.Strings).
  • Changes:
    • Moved SMTP2HTTPBridge to the com.ibm.soap.server package.
    • The com.ibm.cs.net.TcpTunnelGui has been improved to make it quite a bit nicer (same functionality yet).
    • The SOAPMappingRegistry will now only pre-register XMI-related serialization/deserialization components if running under JDK1.2.2. This way, if the XMI encoding style is specified at runtime, an appropriate error msg will be generated. Previously, a NoClassDefFoundError was being generated.
    • The demos.soapovermail.SOAPMsgOverMail demo will now use the Call class's SOAPTransport property to set the transport to SMTP. It was previously duplicating some of the logic contained in Call.invoke(url, ...).
  • Bug fixes:
    • Fixed ServiceManager.queryService(String id) to return a null if passed a null. Was previously throwing a NullPointerException if given a null. Was causing rpcrouter.jsp to throw a NullPointerException in the case when a client neglects to specify a namespaceURI for an rpc call element (i.e. the request).
    • demos.stockquote.StockQuoteClient.class was out of date. The source had been changed, but had not been re-compiled before building the distribution.
    • deploy.jsp and list.jsp will no longer use <jsp:forward> to show details.jsp. This was causing some JSPv1.0 implementations to choke on <jsp:param>, which was contained in our <jsp:forward> element.

• Version 1.0:
  • Base version. No changes.