RE: doc/lit question

e wsdl:parts. > > My understanding of these rules is that they limit the body of doc/lit > messages to at most one part. The header is an optional additional allowed > part. > > -Original Message- > From: Chris Williamson [mailto:[EMAIL PROTECTED] > Sent: Monday,

RE: doc/lit question

t; > At 11:10 AM 9/29/2003 -0400, you wrote: > > >R2201 A document-literal binding in a DESCRIPTION MUST, in each of its > >soapbind:body > >element(s), have at most one part listed in the parts attribute, if the > >parts attribute is specified. > > > &g

doc/lit question

Is it legal to have two parts in a doc/lit call? It appears to be legal in the ws-i spec. Am I right there? Is this supported by Axis? You could probably do this by building the SOAP messages from scratch right? But is it supported in WSDL2Java or anything like that? Thanks, Chris

RE: namespace question

Excellent thanks Anne. That is a big help. So that means that if the form is qualified it takes on the targetNamespace. I think I got it. Thanks, Chris > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Friday, September 26, 2003 3:50 PM > To: [EMAIL PROTE

RE: array question

ement] attribute respectively on any collection type. The default is [XmlArray]."Chris Williamson" <[EMAIL PROTECTED]> wrote:Hey I have a question about arrays. In the ws-i spec it states that arrays should be defined such as... maxOccurs="unbounded&

array question

Hey I have a question about arrays. In the ws-i spec it states that arrays should be defined such as... And this turns out... blah moreblah Should arrays be defined in a complexType all to themselves? Or I noticed that Axis supports something like this...

RE: namespace question

ase see my answers below. > > Gary > > > -----Original Message- > > From: Chris Williamson [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 26, 2003 9:35 AM > > To: [EMAIL PROTECTED] > > Subject: RE: namespace question > > > > > > I

RE: namespace question

Yeah I just wasn't sure if there are specific benefits of either way. I guess it is message size vs. stricter validation. Thanks again. Chris > -Original Message- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Friday, September 26, 2003 12:01 PM > To: [EMAIL PROTECTED] > S

RE: namespace question

I have a few followup questions about this. 1) What is the preferred way to do this? Is it preferred to use elementFormDefault="qualified" or not? Is there anything mentioned about this in ws-i or any other spec that tries to standardize web services? 2) So if elementFormDefault="qualified" is

RE: namespace question

Gary and Anne, Thanks for the excellent answers. I was not aware of this attribute and it all now makes complete sense. I was confused because the TerraService web service (if you have ever seen it) requires qualified namespaces whereas the axis examples I was working with do not. And I was beg

namespace question

Hello, I have a question about namespaces while using document style web service... Say I have a method defined by the schema... http://www.domain.com/namespace"; xmlns="http://www.w3.org/2001/XMLSchema";> ... It appears that the code that is generate

echo example document style

So the targetNamespace will be important. Is it even possible to convert the echo example into using wrapped style at this point? It would be a nice useful example. Thanks for any help, Chris Williamson

schema questions

I have heard rumblings of new schema functionality. What exactly is this new functionality? Where can I go to read about it? I am looking to validate a SOAPEnvelope I build up. Is this something I can do with this new functionality? Is this something I can do anyway. I got stuck trying to do

RE: examples

Microsoft and IBM have a few that are okay. Microsoft has a partnership with mapquest. You are required to pay for the service, but they have a trial license available. They also have a Terra Service for free. Both of these seem like nice examples, although I haven't delved very deep into using

RE: addAttribute/setType problem

I honestly think there are several bugs in MessageElement and I have not had anyone tell me differently in the last few days. I am probably going to submit the bugs I have found to bugzilla today. I have around seven that are all related to MessageElement. Kind of scary. Plus, these are all rel

RE: addAttribute/setType problem

o not accomplish all that they mean to accomplish. Could someone with some knowledge on this class, please let me know if I am way off on this. If not, what is the best route to proceed in fixing this. I could not find this in bugzilla. Shall I submit a bug? Thanks, for any help. Chris Willi

addAttribute/setType problem

e a way to generate a unique namespace? I have included two SOAPEnvelopes...the first is what I wish to get and what I get when I print out the message the first time while using addAttribute. The second message is what I get when I print the SOAPEnvelope the second time. Thanks, Chris Williamso