RE: Web service issue

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: larry franks (larryfr_at_online.microsoft.com)
Date: 08/11/04


Date: Wed, 11 Aug 2004 17:42:04 GMT

Hi Ian, this is by design. We use XML serialization (from the .net
namespace) to put the message into the messagebox. XML serialization knows
about the schema and if there is an element that contains a value matching
the default value then it won't be serialized as the schema already
describes it.
I think this may be a SOAP standard thing based on serialization rule 9
listed at http://www.w3.org/TR/2001/WD-soap12-part2-20011217/#encrules ,
but at the least it's by design in the serializer we use.

If you need to populate fields with a default value and you're using SOAP,
then you'll need to use a map or logic in an orchestration to check for an
empty element and fill in the value you want.

If you'd like to change this behavior you can open a case with Microsoft
Product Support Services and file a design change request against the
product. You can also send mail to ebizwish@microsoft.com detailing this
issue and suggesting that this be changed for future versions of the
product.

Larry Franks

This posting is provided "AS IS" with no warranties,and confers no rights.
Subscribe at
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
--------------------
| Thread-Topic: Web service issue
| thread-index: AcR/vYSaFInuIsEJSR2+3GqUfoqdDg==
| X-WBNR-Posting-Host: 194.63.116.72
| From: =?Utf-8?B?aWFuLnRob21hc0BvbmxpbmUubm9zcGFt?=
<ian.thomas@online.nospam>
| References: <B1B6C115-8D2E-4EC3-AE5D-D7FE7063032C@microsoft.com>
| Subject: RE: Web service issue
| Date: Wed, 11 Aug 2004 09:09:02 -0700
| Lines: 55
| Message-ID: <0A50CA70-4542-4624-AD79-24790A75EFA5@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.biztalk.general
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:18335
| X-Tomcat-NG: microsoft.public.biztalk.general
|
| Some extra information that I've worked out since:
|
| - The extra information was appearing because there were mandatory fields
I
| hadn't set which the soap toolkit was obviously creating elements for
| - The data that I've set up in the message via the transform only
disappears
| from the soap message if the values are the default ones
|
| Hence i still have a problem but it's slightly different: for some reason
| whenever I set elements up in the message that have the default values
the
| soap infrastructure seems to ignore them and not send them to the server.
 In
| order to test this propostion I have set the elements to non-default
values
| in the transform instead and these are successfully passed to the server.
|
| Why would default values that I have explicitly set in the message not
turn
| up in the soap message?
|
| Thanks again
|
| Ian
|
| "ian.thomas@online.nospam" wrote:
|
| > Hi,
| >
| > I'm currently having a problem that is driving me nuts and I was hoping
| > someone has experienced something similar.
| >
| > I've basically got an orchestration that is exposes a port as a web
service.
| >
| > I then have a second orchestration that consumes this web service with
a
| > message of the type generated by the web reference created from the
wsdl of
| > the consumed service.
| >
| > The issue is that although I use a transform to set up the parameters
in the
| > message to be sent to the web service by the time the message arrives
at the
| > invoked orchestration some of the data is still there, some has
disappeared
| > completely and some new data has appeared.
| >
| > I have debugged the orchestration and just before the send shape I can
| > confirm that the message to be despatched to the web service does have
the
| > correct data in it. I have then also debugged the invoked
orchestration and
| > confirmed that the message is incorrect by the time it is received.
| > Interestingly, though, I have also used the soap toolkit to examine the
| > message on the wire and the incorrect message is being sent, so it
would
| > appear to be a problem at the sending end.
| >
| > As a result it would seem that sometime between the creation of the
message
| > to be sent and the actual physical building of the soap message the
| > underlying engine is messing up my message.
| >
| > Anybody got any ideas why this might be happening?
| >
| > Help!
| >
| > Ian
|



Relevant Pages

  • RE: Web service issue
    ... from the soap message if the values are the default ones ... > I've basically got an orchestration that is exposes a port as a web service. ... > Interestingly, though, I have also used the soap toolkit to examine the ...
    (microsoft.public.biztalk.general)
  • The Messaging Engine failed to register the adapter for SOAP
    ... "The Messaging Engine failed to register the adapter for SOAP" ... have to change Orchestration Receive port to newly created SOAP ... Before this you make sure that your web service run under proper ...
    (microsoft.public.biztalk.general)
  • Re: receive and send without orchestration
    ... If you have a one-way SOAP send port i.e. no response message this should be ... Just create two SOAP send ports and set the same Filter in each. ... If you are receiving a return message from the web service it gets trickier. ... to two web services, without using an orchestration? ...
    (microsoft.public.biztalk.general)
  • Re: Using SOAP Receive location adds additional conditions in subscrip
    ... that case you assumption is correct - BizTalk tightly ties the orchestration ... My web service just forwards the untyped ... Then a receive location is configured using the SOAP adapter and my ...
    (microsoft.public.biztalk.general)
  • Re: Web Services and COBOL (Fairly long post, but I dont have time to write a proper article on it)
    ... Web Service is a great prerequisite for automated client-side code ... generation in the mainstream Java and .NET SOAP frameworks. ... $set Repository Update ... 000464 12 objSOAPClient OBJECT REFERENCE. ...
    (comp.lang.cobol)