Hi,
I have a web service which returns a record set and works well integrated
with an asp dot net page.
However if I decided to develop a unix app
will i be able to read the dataset as it is
or do i need to write the xml as text from the web service and supply a DTD.
Also any other pitfalls
TIA
Stu
7  5994 
Dataset will always pose major problems with interoperablity because
difgramm is unique to .Net framework only. If you cannot do anything to
change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your dataset
contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when designing a
web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote: Hi,
I have a web service which returns a record set and works well integrated
with an asp dot net page.
However if I decided to develop a unix app
will i be able to read the dataset as it is
or do i need to write the xml as text from the web service and supply a DTD.
Also any other pitfalls
TIA
Stu
I agree that a DataSet is problematic for interoperability. Instead return an
XmlElement. Just use the DataSet WriteXml method to a write the DataSet out
to a stream and get the root element.
Of course, if the DataSet has changed, be sure to call AcceptChanges first.
Chris Rolon
"erymuzuan" wrote: Dataset will always pose major problems with interoperablity because
difgramm is unique to .Net framework only. If you cannot do anything to
change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your dataset
contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when designing a
web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote: Hi,
I have a web service which returns a record set and works well integrated
with an asp dot net page.
However if I decided to develop a unix app
will i be able to read the dataset as it is
or do i need to write the xml as text from the web service and supply a DTD.
Also any other pitfalls
TIA
Stu
Erymuzuan's approach allows much better control over the XML
serialization format of the data. Since the original post was about
interoperating with a different platform, that level of control may be
crucial to getting the web services to talk to each other. A DataSet
expressed in XML is still a DataSet ;)
You also already hint on another issue. The DataSet offers a very
convenient programming model that doesn't jive well with
interoperability. You will have to write to code anyway to make that
programming model work for externally exposed Web services. Programming
against serialized objects will also help gearing the code inside the
service more towards interoperability.
Just my toughts.
HTH,
Christoph Schittko
MVP XML http://weblogs.asp.net/cschittko -----Original Message-----
From: Chris Rolon [mailto:Ch********@discussions.microsoft.com]
Posted At: Sunday, January 23, 2005 9:51 AM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
I agree that a DataSet is problematic for interoperability. Instead
return an
XmlElement. Just use the DataSet WriteXml method to a write the
DataSet out
to a stream and get the root element.
Of course, if the DataSet has changed, be sure to call AcceptChanges
first.
Chris Rolon
"erymuzuan" wrote:
Dataset will always pose major problems with interoperablity because
difgramm is unique to .Net framework only. If you cannot do anything
to change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your
dataset contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when designing
a web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote: Hi,
I have a web service which returns a record set and works well integrated with an asp dot net page.
However if I decided to develop a unix app
will i be able to read the dataset as it is
or do i need to write the xml as text from the web service and
supply a DTD. Also any other pitfalls
TIA
Stu
This sort of problem posted again and again in this newsgroup simply
because some of us thinks that Web Services is just a method with
WebMethod attribute, rather that a set of messages in a document based
mesaging platform. even a simple web method like this can cause
interoperablity problem
[WebMethod]
public Employee[] GetEmployee()
{
Employee[] emps = new Employee[10];
return emps;
}
I think Microsoft is part to blame for making developers thinking that's
how to write web services. everytime you create a new asmx in VS.Net in
give the HelloWord
// WEB SERVICE EXAMPLE
// The HelloWorld() example service returns the string Hello World
// To build, uncomment the following lines then save and build the project
// To test this web service, press F5
// [WebMethod]
// public string HelloWorld()
// {
// return "Hello World";
// }
Using tools like XmlSpy (my favorite) or CapeClear WSDL editor certainly
helps to make a better interoperable web services. Christian Weyer's
contract-first tool for web services is a great tool to achieve this as
well, thou' i have it installed never really touch it. One of this
should be the first tool every web service developer should have in
their toolbox after the HelloWorld introduction
regards
erymuzuan
Christoph Schittko [MVP] wrote: Erymuzuan's approach allows much better control over the XML
serialization format of the data. Since the original post was about
interoperating with a different platform, that level of control may be
crucial to getting the web services to talk to each other. A DataSet
expressed in XML is still a DataSet ;)
You also already hint on another issue. The DataSet offers a very
convenient programming model that doesn't jive well with
interoperability. You will have to write to code anyway to make that
programming model work for externally exposed Web services. Programming
against serialized objects will also help gearing the code inside the
service more towards interoperability.
Just my toughts.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
-----Original Message-----
From: Chris Rolon [mailto:Ch********@discussions.microsoft.com]
Posted At: Sunday, January 23, 2005 9:51 AM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
I agree that a DataSet is problematic for interoperability. Instead
return
an
XmlElement. Just use the DataSet WriteXml method to a write the
DataSet
out
to a stream and get the root element.
Of course, if the DataSet has changed, be sure to call AcceptChanges
first.
Chris Rolon
"erymuzuan" wrote:
Dataset will always pose major problems with interoperablity because
difgramm is unique to .Net framework only. If you cannot do anything
to
change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your
dataset
contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when designing
a
web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote:
Hi,
I have a web service which returns a record set and works well
integrated
with an asp dot net page.
However if I decided to develop a unix app
will i be able to read the dataset as it is
or do i need to write the xml as text from the web service and
supply
a DTD.
Also any other pitfalls
TIA
Stu
Thanks for all your response on this
I like the dataset model cuase its very quick and convenient.
So ill probably end up putting some method overrides so u can choose dataset
or xml
Stu
"erymuzuan" wrote: This sort of problem posted again and again in this newsgroup simply
because some of us thinks that Web Services is just a method with
WebMethod attribute, rather that a set of messages in a document based
mesaging platform. even a simple web method like this can cause
interoperablity problem
[WebMethod]
public Employee[] GetEmployee()
{
Employee[] emps = new Employee[10];
return emps;
}
I think Microsoft is part to blame for making developers thinking that's
how to write web services. everytime you create a new asmx in VS.Net in
give the HelloWord
// WEB SERVICE EXAMPLE
// The HelloWorld() example service returns the string Hello World
// To build, uncomment the following lines then save and build the project
// To test this web service, press F5
// [WebMethod]
// public string HelloWorld()
// {
// return "Hello World";
// }
Using tools like XmlSpy (my favorite) or CapeClear WSDL editor certainly
helps to make a better interoperable web services. Christian Weyer's
contract-first tool for web services is a great tool to achieve this as
well, thou' i have it installed never really touch it. One of this
should be the first tool every web service developer should have in
their toolbox after the HelloWorld introduction
regards
erymuzuan
Christoph Schittko [MVP] wrote: Erymuzuan's approach allows much better control over the XML
serialization format of the data. Since the original post was about
interoperating with a different platform, that level of control may be
crucial to getting the web services to talk to each other. A DataSet
expressed in XML is still a DataSet ;)
You also already hint on another issue. The DataSet offers a very
convenient programming model that doesn't jive well with
interoperability. You will have to write to code anyway to make that
programming model work for externally exposed Web services. Programming
against serialized objects will also help gearing the code inside the
service more towards interoperability.
Just my toughts.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
-----Original Message-----
From: Chris Rolon [mailto:Ch********@discussions.microsoft.com]
Posted At: Sunday, January 23, 2005 9:51 AM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
I agree that a DataSet is problematic for interoperability. Instead
return
an
XmlElement. Just use the DataSet WriteXml method to a write the
DataSet
out
to a stream and get the root element.
Of course, if the DataSet has changed, be sure to call AcceptChanges
first.
Chris Rolon
"erymuzuan" wrote:
Dataset will always pose major problems with interoperablity because
difgramm is unique to .Net framework only. If you cannot do anything
to
change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your
dataset
contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when designing
a
web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote:
>Hi,
>
>I have a web service which returns a record set and works well
integrated
>with an asp dot net page.
>However if I decided to develop a unix app
>will i be able to read the dataset as it is
>or do i need to write the xml as text from the web service and
supply
a DTD.
>Also any other pitfalls
>
>TIA
>
>Stu
I agree with all of that ;)
Glad to hear you like wscf. Have you taken a look at release 0.4
(released last December) with the new WSDL wizard? We'd love to hear
what you think.
Christoph Schittko
MVP XML http://weblogs.asp.net/cschittko -----Original Message-----
From: erymuzuan [mailto:er*******@yahoo.com]
Posted At: Sunday, January 23, 2005 6:22 PM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
This sort of problem posted again and again in this newsgroup simply
because some of us thinks that Web Services is just a method with
WebMethod attribute, rather that a set of messages in a document based
mesaging platform. even a simple web method like this can cause
interoperablity problem
[WebMethod]
public Employee[] GetEmployee()
{
Employee[] emps = new Employee[10];
return emps;
}
I think Microsoft is part to blame for making developers thinking
that's how to write web services. everytime you create a new asmx in VS.Net
in give the HelloWord
// WEB SERVICE EXAMPLE
// The HelloWorld() example service returns the string Hello World
// To build, uncomment the following lines then save and build the
project // To test this web service, press F5
// [WebMethod]
// public string HelloWorld()
// {
// return "Hello World";
// }
Using tools like XmlSpy (my favorite) or CapeClear WSDL editor
certainly helps to make a better interoperable web services. Christian Weyer's
contract-first tool for web services is a great tool to achieve this
as well, thou' i have it installed never really touch it. One of this
should be the first tool every web service developer should have in
their toolbox after the HelloWorld introduction
regards
erymuzuan
Christoph Schittko [MVP] wrote: Erymuzuan's approach allows much better control over the XML
serialization format of the data. Since the original post was about
interoperating with a different platform, that level of control may
be crucial to getting the web services to talk to each other. A DataSet
expressed in XML is still a DataSet ;)
You also already hint on another issue. The DataSet offers a very
convenient programming model that doesn't jive well with
interoperability. You will have to write to code anyway to make that
programming model work for externally exposed Web services.
Programming against serialized objects will also help gearing the code inside
the service more towards interoperability.
Just my toughts.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
-----Original Message-----
From: Chris Rolon [mailto:Ch********@discussions.microsoft.com]
Posted At: Sunday, January 23, 2005 9:51 AM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
I agree that a DataSet is problematic for interoperability. Instead
return
an
XmlElement. Just use the DataSet WriteXml method to a write the
DataSet
out
to a stream and get the root element.
Of course, if the DataSet has changed, be sure to call AcceptChanges
first.
Chris Rolon
"erymuzuan" wrote:
Dataset will always pose major problems with interoperablity
becausedifgramm is unique to .Net framework only. If you cannot do
anything
to
change the web services, then you'll have to process the dataset as
XmlDocument on other platforms. and this could be tricky if your
dataset
contains lot of diffgram information.
The best way is avoid dataset, try to think in schema when
designing
a
web services. all you have to do is create a schema first then use
xsd.exe to generate .net code that can be used in web services.
regards
erymuzuan
Stu wrote:
>Hi,
>
>I have a web service which returns a record set and works well
integrated
>with an asp dot net page.
>However if I decided to develop a unix app
>will i be able to read the dataset as it is
>or do i need to write the xml as text from the web service and
supply
a DTD.
>Also any other pitfalls
>
>TIA
>
>Stu
One final question
Forgive my ignorance on the Unix Side of but if i have an ms web service say
function xyz(a,b,c,d) will they be able to use the proxy and call the web
service or do I need to process xml soap streams ?
Any good resources for dev MS web services for unix
"Christoph Schittko [MVP]" wrote: I agree with all of that ;)
Glad to hear you like wscf. Have you taken a look at release 0.4
(released last December) with the new WSDL wizard? We'd love to hear
what you think.
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
-----Original Message-----
From: erymuzuan [mailto:er*******@yahoo.com]
Posted At: Sunday, January 23, 2005 6:22 PM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: calling a dot net web services from unix
Subject: Re: calling a dot net web services from unix
This sort of problem posted again and again in this newsgroup simply
because some of us thinks that Web Services is just a method with
WebMethod attribute, rather that a set of messages in a document based
mesaging platform. even a simple web method like this can cause
interoperablity problem
[WebMethod]
public Employee[] GetEmployee()
{
Employee[] emps = new Employee[10];
return emps;
}
I think Microsoft is part to blame for making developers thinking
that's how to write web services. everytime you create a new asmx in VS.Net
in give the HelloWord
// WEB SERVICE EXAMPLE
// The HelloWorld() example service returns the string Hello World
// To build, uncomment the following lines then save and build the
project // To test this web service, press F5
// [WebMethod]
// public string HelloWorld()
// {
// return "Hello World";
// }
Using tools like XmlSpy (my favorite) or CapeClear WSDL editor
certainly helps to make a better interoperable web services. Christian Weyer's
contract-first tool for web services is a great tool to achieve this
as well, thou' i have it installed never really touch it. One of this
should be the first tool every web service developer should have in
their toolbox after the HelloWorld introduction
regards
erymuzuan
Christoph Schittko [MVP] wrote: Erymuzuan's approach allows much better control over the XML
serialization format of the data. Since the original post was about
interoperating with a different platform, that level of control may be crucial to getting the web services to talk to each other. A DataSet
expressed in XML is still a DataSet ;)
You also already hint on another issue. The DataSet offers a very
convenient programming model that doesn't jive well with
interoperability. You will have to write to code anyway to make that
programming model work for externally exposed Web services. Programming against serialized objects will also help gearing the code inside the service more towards interoperability.
Just my toughts.
HTH,
Christoph Schittko
MVP XML
http://weblogs.asp.net/cschittko
>-----Original Message-----
>From: Chris Rolon [mailto:Ch********@discussions.microsoft.com]
>Posted At: Sunday, January 23, 2005 9:51 AM
>Posted To: microsoft.public.dotnet.framework.webservices
>Conversation: calling a dot net web services from unix
>Subject: Re: calling a dot net web services from unix
>
>I agree that a DataSet is problematic for interoperability. Instead
return
>an
>XmlElement. Just use the DataSet WriteXml method to a write the
DataSet
>out
>to a stream and get the root element.
>
>Of course, if the DataSet has changed, be sure to call AcceptChanges
>first.
>
>Chris Rolon
>
>"erymuzuan" wrote:
>
>
>>Dataset will always pose major problems with interoperablity because>>difgramm is unique to .Net framework only. If you cannot do anything
to
>>change the web services, then you'll have to process the dataset as
>>XmlDocument on other platforms. and this could be tricky if your
dataset
>>contains lot of diffgram information.
>>
>>The best way is avoid dataset, try to think in schema when designing
a
>>web services. all you have to do is create a schema first then use
>>xsd.exe to generate .net code that can be used in web services.
>>
>>regards
>>erymuzuan
>>
>>Stu wrote:
>>
>>>Hi,
>>>
>>>I have a web service which returns a record set and works well
>
>integrated
>
>>>with an asp dot net page.
>>>However if I decided to develop a unix app
>>>will i be able to read the dataset as it is
>>>or do i need to write the xml as text from the web service and
supply
>a DTD.
>
>>>Also any other pitfalls
>>>
>>>TIA
>>>
>>>Stu
>>
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: Amit |
last post by:
I tried calling a subroutine in a fortran module from C ,but couldn't.I
always get the error: undefined reference in the main.o file (main is
in C calling the subroutine).
for calling the...
|
by: Bryan |
last post by:
I have a multi-threaded C# console application that uses WMI
(System.Management namespace) to make RPC calls to several servers (600+ )
and returns ScheduledJobs. The section of my code that...
|
by: Dan V. |
last post by:
Is there a way to query a remote xml file periodically by not using web
services? For Windows and Unix platforms. Is there a cheap software product
that I can install on each client and my Windows...
|
by: zlatko |
last post by:
Hello. I am new to .net .
I have a managed C++ library. It looks like this.
// header file
namespace cppnetdll
{
public __gc class Class1
{
public:
static int foo_int(void);
|
by: Cleo |
last post by:
Hi,
I am trying to call a WebService Method written in Weblogic from VB.NET and
I am getting the following error. I am using SOAP Caal s from VB.NET.
Please find the wsdl file and my code.
...
|
by: Jerome Cohen |
last post by:
AI am trying to call a third-party web service. this service expects an XML
fragment that contains the request plus other parameter. adding the web
reference created the syntax below(reference.vb)....
|
by: Iter |
last post by:
Hi Guys,
In my company, we have java application which is runing in unix platform,
and we have web service application build by microsoft .net runing in IIS in
microsoft windows 2000 platform....
|
by: jens Jensen |
last post by:
Hello ,
i'm calling a webservice generated with oracle webservice java tools.
I'm not able to add a web reference to a .net client the usual way with
visual studio 2005.
I was therefore...
|
by: amitpatel66 |
last post by:
There is always a requirement that in Oracle Applications, the Concurrent Program need to be execute programatically based on certain conditions/validations:
Concurrent programs can be executed...
|
by: taylorcarr |
last post by:
A Canon printer is a smart device known for being advanced, efficient, and reliable. It is designed for home, office, and hybrid workspace use and can also be used for a variety of purposes. However,...
|
by: ryjfgjl |
last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: marktang |
last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
| |
