Title: RE: XML and web services
I think I understand your argument, Ricky, but here is the deal. My web service performs the job of processing numerous types of database queries, too numerous to describe in a static API. The best way to describe the queries requested is to provide an XML
Barry Lulas wrote:
I'm just trying to find the best way to describe the datatype that
holds the XML documents.
For example, my java interface for the web service may look like this:
public interface IMyInterface
{
public String executeQuery(String query);
Title: RE: XML and web services
I get the following error message when using the Document version:
The class org.w3c.dom.Document does not contain a default constructor, which is a requirement for a bean class. The class cannot be converted into an xml schema type. An xml schema anyType
Barry Lulas wrote:
The class org.w3c.dom.Document does not contain a default constructor,
which is a requirement for a bean class. The class cannot be
converted into an xml schema type. An xml schema anyType will be used
to define this class in the wsdl file.
Any way around this?
, October 30, 2002 12:00 PM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
Barry,
We've used services that received and returned Documents before. The
.wsdd for this has to set
provider=java:MSG
instead of java:RPC. Also -- depending on which version of Axis you're
using -- you may find
Title: XML and web services
I realize this is an Axis user group, but I wanted to pick your brains on a related issue.
I have a generic web service that I deploy via Axis. The web service takes in an XML file as a request and returns an XML file as a response. My question is what
The best way in theory is to simply pass DOMs in whichever languages you
are using. The SOAP engine then uses literalXML encoding to make it
happen - but this functionality is broken in Axis at the moment it
appears, and seems to have been for some time.
This is really quite a serious issue if
Title: RE: XML and web services
Thanks Mike, keep me informed as to the status.
-Original Message-
From: Mike Hearn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 29, 2002 9:02 AM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
The best way in theory is to simply pass
Title: RE: XML and web services
how do clients pass the xml file as a byte-array?
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 29, 2002 9:51 AM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
Barry Lulas wrote:
I realize
Title: RE: XML and web services
James,
What does your web service interface look like? I like the idea of having multiple options
Barry Lulas
[EMAIL PROTECTED]
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 29, 2002 11:12 AM
To: [EMAIL
Barry Lulas wrote:
What does your web service interface look like? I like the idea of
having multiple options
I have an input bean where the options are set regarding the graph
type that is desired (setting what is on the x, y, z axes and how to
group the data). There is also a byte
Title: RE: XML and web services
i see. what does the java interface look like?
-Original Message-
From: James Black [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 29, 2002 11:40 AM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
Barry Lulas wrote:
What does your web
Barry Lulas wrote:
i see. what does the java interface look like?
public byte[] getGraph(EpicVisitor input, byte retmode)
Besides the performance overhead of converting the XML to a byte array and
back, another big minus is the WSDL in this case has lost all the schema
definition. In other words, the client and the server has to use another
channel to communicate what does the detail of the request and response
Ricky Ho wrote:
Besides the performance overhead of converting the XML to a byte array and
back, another big minus is the WSDL in this case has lost all the schema
definition. In other words, the client and the server has to use another
channel to communicate what does the detail of the
)
Subject:Re: XML and web services
This has the issue as the previous one that the schema structure of the DOM
tree is undefined in the WSDL.
Rgds, Ricky
At 02:41 PM 10/29/2002 -0500, [EMAIL PROTECTED] wrote:
Doesn't this all seem complex compared to just supporting an XML datatype
respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED], [EMAIL PROTECTED]
cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:Re: XML and web services
This has the issue as the previous one that the schema structure of the DOM
tree is undefined in the WSDL.
Rgds, Ricky
At 02:41 PM 10/29/2002
17 matches
Mail list logo
