s?
>
> -Original Message-
> From: James Black [mailto:jblack@;ieee.org]
> Sent: Wednesday, October 30, 2002 11:05 AM
> To: [EMAIL PROTECTED]
> Subject: Re: XML and web services
>
>
> Barry Lulas wrote:
>
> > I'm just trying to find the best way to descr
nks for the response. So how do you manage the provider, is this a
parameter in the Java2WSDL class?
Thanks!
-Original Message-
From: Steven Gollery [mailto:
Sent: Wednesday, October 30, 2002 12:00 PM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
Barry,
We've used serv
dl file.
Any way around this?
-Original Message-
From: James Black [mailto:jblack@;ieee.org ]
Sent: Wednesday, October 30, 2002 11:05 AM
To: [EMAIL PROTECTED]
Subject: Re: XML and web services
Barry Lulas wrote:
> I'm just trying to find the best way to describe the datatype tha
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?
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:
> 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 qu
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
<[EMAIL PROTECTED]> on 10/29/2002 05:06:49 PM
Please 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
ystems/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 -0500, [EMAIL PROTECTED] wrote:
>Doesn't this all seem complex compared to just support
EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:Re: XML and web services
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
tentially custom handlers).
Kevin
James Black <[EMAIL PROTECTED]> on 10/29/2002 01:26:41 PM
Please respond to [EMAIL PROTECTED]
To:[EMAIL PROTECTED]
cc: (bcc: Kevin Bedell/Systems/USHO/SunLife)
Subject:Re: XML and web services
Ricky Ho wrote:
> Besides the performance
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 r
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
l
Barry Lulas wrote:
> i see. what does the java interface look like?
public byte[] getGraph(EpicVisitor input, byte retmode)
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 y
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 p
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
"Weakliem, Gordon" wrote:
> If you're doing document/literal, both string and byte[] are bad approaches
> anyway. You take a hit on the encoding step, both in the conversion (memory
> and processor) and on the wire, because base 64 is bigger, and you take a
> hit to zip it if you try to alleviat
is out of band. The right
approach long term is to leave it as XML, you could do String or byte[] as a
temporary workaround, but it's a bad general solution.
-Original Message-
From: James Black [mailto:jblack@;ieee.org]
Sent: Tuesday, October 29, 2002 8:28 AM
To: [EMAIL PROTECTED]
Su
A CDATA section in the XML you're trying to send back and forth? If you
try to send invalid XML, or stuff that conflicts with the SOAP wrappers
then yeah, I can see that, but what if you just want to send some
simple elements with attributes?
James Black wrote:
Mike Hearn wrote:
Mike Hearn wrote:
> I assume you're referring to character encoding issues here? I don't
> understand what problems the soap wrapper could cause..
From what I understand, when using a CDATA element, for example, there
can be things that will cause some problems with the XML parser that is
Barry Lulas wrote:
> how do clients pass the xml file as a byte-array?
In Java it is pretty easy, just call the getBytes method, and it will
return the array of bytes that represents the string.
I assume you're referring to character encoding issues here? I don't
understand what problems the soap wrapper could cause..
James Black wrote:
Barry Lulas wrote:
I realize this is an Axis user group, but I wanted to pick your brains
on a related issue.
I have a generic web
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 t
Barry Lulas wrote:
> 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 is the best
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
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
27 matches
Mail list logo
