Thanx Anne, so this means that I also will have no problems with attributes using axis the rpc/literal way, right?
Am Donnerstag 12 Juni 2003 22:49 schrieb Anne Thomas Manes: > The SOAP spec prohibits the use of attributes in RPC/encoded messages. > > From SOAP Section 5 [1]: > > The rules for serialization are as follows: > > 1. All values are represented as element content. > > Perhaps this is the source of confusion? Document/Literal definitely > supports attributes, though, and the Axis serializer should handle it. > > Note that the JAX-RPC 1.0 XML to Java Mapping (Chapter 4) is based on SOAP > Encoding, therefore doesn't necessarily apply to Document/Literal. From > page 21: > "Note that the rules and format of serialization for XML data types > are based on the encoding style." > > The example shown on page 58 is simply an example -- not a specification. > As it says, the JAX-RPC 1.0 spec does not specify how to map an attribute. > (It is very RPC/Encoded-centric.) That means it's left to the implementor > to figure out how to do it. > > [1] http://www.w3.org/TR/SOAP/#_Toc478383512 > > Anne > > ----- Original Message ----- > From: "Herrick, Mike" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, June 12, 2003 3:55 PM > Subject: RE: support of xml attributes > > > WSDL2Java might not choke on it, but does Axis serialize/deserialize it @ > > run time? > > > I am far from an Axis expert. I tried this at one point, had problems, > > referred to the spec and decided to stay away from attributes. > > > Mike > > > > -----Original Message----- > > From: Michael Zurke [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 12, 2003 12:46 PM > > To: [EMAIL PROTECTED] > > Subject: Re: support of xml attributes > > > > > > mike: using axis 1-1RC2 i had no problem using WSDL2Java even if there > > were > > > attributes in my schema. are you're sure that axis has problems with > > that? mischa > > > > Am Donnerstag 12 Juni 2003 21:15 schrieb Herrick, Mike: > > > My understanding is that attributes get converted to SOAPElements as > > > defined by the JAX-RPC spec. > > > > > > "The JAX-RPC specification does not specify a standard Java mapping for > > a > > > > xsd:complexType with the xsd:attribute. So the message part in the > > > DoAnotherExample message is mapped as a SOAPElement." see page 58 of > > > the 1.0 spec. > > > > > > So there isn't anything really from stopping you from using them, > > > you'll just have to write more code. > > > > > > I just stay away from attributes so that I can use WSDL2Java and be > > > done with it ... I don't want to have to write the > > serialization/deserialization > > > > stuff, have better things to do. What is the point of using an IDL > > language > > > > (WSDL) if you can't even have it autogen for you? > > > > > > Anyway, would be nice if some day the spec changed on this, but until > > then > > > > I'd recommend staying away from attributes. You'll get more sleep. > > > > > > Mike > > > > > > -----Original Message----- > > > From: Michael Zurke [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, June 12, 2003 12:05 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re:Re: support of xml attributes > > > > > > > > > it's not that i already got a problem with axis. as i said..i just > > > heard about that direction of lacking support of attributes for > > > releases in > > the > > > > future. how about that? > > > > > > mischa > > > > > > Can you send me the XML schema sample you have that may not > > > work with AXIS WSDL/Java ? > > > > > > Michael Zurke <[EMAIL PROTECTED]> wrote: > > > hello, > > > > > > i heard that some ws-tool-vendors do not support attributes in xml > > schema. > > > > i also heard that axis will go in the same direction. does anybody have > > > some information about how the future will look like regarding this > > point. > > > > in need that information to keep the compatibility of my xml-schemas > > with > > > > further versions of axis. > > > > > > thanx, > > > > > > mischa > > > > > > --------------------------------- > > > Do you Yahoo!? > > > Free online calendar with sync to Outlook(TM).
