You might want to changed data format to text format and then send it in xml.
> I've been asking around and reading but I cannot find a definitive answer. I
> have customers that need information from our calendar application. The
[quoted text clipped - 6 lines]
>
> Thanks.
Hi,
this is a nice example of why a lot of people are shouting; "Contract
first design!!!".
By doing all the contracts (Schema & WSDL) design first you will never
use anything that the official WebServices stack disallows. This
doesn't mean you won't run into issues, but these issues will then be
related to the chosen toolkit for implementing the code, but never an
DATATYPE inconsistency issue.
Define all your structures & data-classes in XSD first. and keep to
the rule; the more explicit type, the better.. (Do you define a C#
'string' to hold a date? or DateTime ? the same goes for XSD design).
Hope this helps,
Marvin Smit.
>You might want to changed data format to text format and then send it in xml.
>
[quoted text clipped - 8 lines]
>>
>> Thanks.
Daniel - 09 Nov 2005 13:54 GMT
Marvin - What you said sounds good but I'm lost. I know what the user needs
and have an idea of how to do it but I'm just spinning my wheels here. There
is so much out there but none of it is a great help. Most of the stuff is
the useless "Hello World". We need examples of returning data to users. My
user will pass a unique identifier to my webservice and in turn my webservice
needs to return a set of data.
Any good example of what your talking about Marvin. Thanks for replying.
daniel
> Hi,
>
[quoted text clipped - 27 lines]
> >>
> >> Thanks.
Marvin Smit - 10 Nov 2005 14:00 GMT
Hi,
The advise i'de like to give you is;
Start designing your 'structures'. The ones you'de use in 'a normal
program'. When you got those, write them down in the XSD syntax ;)
Now start defining the interface for your webservice (*just like any
other interface but keep in mind it should not be chatty).
Generate the dataclasses from the XSD you made
Implement the interface in a webservice and use the generated data
classes or (xsd)simpletypes for parameters.
Implement the webmethods (interface methods you designed) like your
normal program.
* Keep in mind that WebServices are stateless.
Hope this helps,
Marvin Smit.
>Marvin - What you said sounds good but I'm lost. I know what the user needs
>and have an idea of how to do it but I'm just spinning my wheels here. There
[quoted text clipped - 38 lines]
>> >>
>> >> Thanks.