Return-Path: Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 30179 invoked by uid 500); 12 Jun 2003 19:28:37 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 30168 invoked from network); 12 Jun 2003 19:28:37 -0000 Message-ID: From: "Herrick, Mike" To: "'axis-user@ws.apache.org'" Subject: RE: Re: support of xml attributes Date: Thu, 12 Jun 2003 12:28:39 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C33118.D06B3E92" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C33118.D06B3E92 Content-Type: text/plain settle down. -----Original Message----- From: Mr. Document Service [mailto:mrdocservice@yahoo.com] Sent: Thursday, June 12, 2003 12:27 PM To: axis-user@ws.apache.org Subject: RE: Re: support of xml attributes are valid XML Schema 1.0 constructs. WS-I Basic Profile mandates the use of XML Schema as the type system for WSDL descriptions of Web Services. It does not seem like AXIS is WS-I Basic Profile compliant. Does anyone know if there are plans to fix this? If AXIS can not support all XML Schema 1.0 constructs then it would be not be useful in a commericial application environment other than as a prove of concept! "Herrick, Mike" wrote: 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:michael.zurke@web.de] Sent: Thursday, June 12, 2003 12:05 PM To: axis-user@ws.apache.org 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 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). _____ Do you Yahoo!? Free online calendar with sync to Outlook(TM). ------_=_NextPart_001_01C33118.D06B3E92 Content-Type: text/html

settle down.

-----Original Message-----
From: Mr. Document Service [mailto:mrdocservice@yahoo.com]
Sent: Thursday, June 12, 2003 12:27 PM
To: axis-user@ws.apache.org
Subject: RE: Re: support of xml attributes

<xsd:attribute ../> are valid XML Schema 1.0 constructs.

WS-I Basic Profile mandates the use of XML Schema as the type system for WSDL descriptions of Web Services.

It does not seem like AXIS is WS-I Basic Profile compliant. Does anyone know if there are plans to fix this? If AXIS can not support all XML Schema 1.0 constructs then it would be not be useful in a commericial application environment other than as a prove of concept!

"Herrick, Mike" <mike_herrick@mentorg.com> wrote:

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:michael.zurke@web.de]
Sent: Thursday, June 12, 2003 12:05 PM
To: axis-user@ws.apache.org
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 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).

Do you Yahoo!?
Free online calendar with sync to Outlook(TM).

------_=_NextPart_001_01C33118.D06B3E92--