Re: Microsoft SOAP Toolkit 3.0 Beta 1 Released
- Last i heard there were no plans for the MSFT toolkits to include SwA
--- In soapbuilders@y..., "njudah" <njudah@y...> wrote:
> Looks like this Beta supports DIME only; which is a bit
> given the ubiquity of MIME - when should we expect to see MIME
> --- In soapbuilders@y..., "Mike Deem" <mikedeem@m...> wrote:
> > It has been a long time coming and it is finally here:
> > http://www.microsoft.com/downloads/release.asp?
> > Thanks to everyone on soapbuilders who helped us create an
> > release!
> > The features of this release are:
> > * You can now send and receive DIME attachments. Attachments are
> > most efficient way to send data such as pictures, XML documents,
> > amounts of text, etc. See the "Handling Attachments" topic in the
> > file for more information.
> > * A "Generic Type Mapper" (GTM) is now provided. The GTM can map
> > to/from the public properties of a COM object and the XML in a
> > message. The WSDL Wizard automatically generates WSDL and WSML
> > describes complex types and registers those types for use with
> > See the "Using the Generic Type Mapper" topic in the help file
> > information.
> > * A SOAPVDIR.CMD script is installed in the MSSOAP\Binaries
> > script can be used to create an IIS virtual directory properly
> > configured to use the SOAP Toolkit 3.0 ISAPI listener and to
> > an existing virtual directory to use the 3.0 ISAPI listener.
> > * WSDL and XML Schema "import" and "include" elements are now
> > * "One way" messages are now supported. These are simply messages
> > which no response is expected. They are identified in the WSDL by
> > absence of an "output" message for an operation.
> > * You can pass a server object instance to the SoapServer object
> from an
> > ASP page using the SoapInvokeEx method. This allows you to
> > the server object with information taken from the Request ASP
> > Session or Application collections, etc.
> > * The elementFormDefault and form attributes are now correctly
> > generating and parsing document/literal format SOAP messages.
> > * You can now replace the built in type mappers with a custom type
> > mapper.
> > * Source for the SOAP Messaging Object (SMO) framework classes is
> > installed with the SOAP Toolkit Samples. The SMO Wizard is no
> > part of the SOAP Toolkit release.
> > * IXMLDOMNodeList parameters can now contain attribute nodes. The
> > attributes will be added to the parameter element in the SOAP
> > * The WSDL Wizard now generates a "client" side WSML file in
> addition to
> > the "server" side WSML. The Client WSML file only contains client
> > type mapper information and does not reveal any information about
> > server side object.
> > * The WSDL Wizard now allows you to save settings in a
> > file, and restore those settings when you regenerate WSDL for a
> > particular server object.
> > * The following XML schema versions are no longer supported:
> > "http://www.w3.org/1999/XMLSchema"
> > "http://www.w3.org/2000/10/XMLSchema"
> > You must use the W3C recommended version:
> > "http://www.w3.org/2001/XMLSchema"
> > == Mike ==
> > Mike Deem
> > SOAP Toolkit Program Manager
> > Microsoft Corporation
> > This posting is provided "AS IS" with no warranties, and confers
> > rights.