Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: The Attributes and the UN-"wrapper" style
Date: Fri, 10 Sep 2004 16:31:48 -0700
Message-ID: 
 <3A83D9BECDDF58468F068F6CA1C36AB90D4162@corpmail.corp.netledger.com>
Thread-Topic: The Attributes and the UN-"wrapper" style
Thread-Index: AcSXZGR4rjkMSkwgQNeR/ZPhWzRCiAAJ3R0g
From: "Liu, Scott" <SLiu@netsuite.com>
To: <axis-user@ws.apache.org>

Hi, All,

There has been discussion about the "wrapper" style and the attributes
in the past. And Axis does not support wrapper element attributes since
JAX-RPC spec says that the wrapper element should not have attributes. I
have no problem with it. But I do like people to clarify the following
questions.

1. I know that it might be against the spec to have attributes for the
wrapper element. But it is such a simple change on Axis to support
attributes (I made minor change on client code generated with Axis tool
and it worked) I am wondering why the JAX-RPC insists that there is no
attributes for the wrapper element (.NET supports the attributes
anyway)? Does anyone know the story behind this?

2. I did not read the whole JAX-RPC spec and so what I said might be
wrong. Correct me if it is the case.

Since attributes are such a big part of xml schema and if I use the
attributes to go with the UN-wrapped style does Axis support it? My test
revealed that it did not with v1.1. Is there a patch or will it be
supported in Axis 1.2 for un-wrapped style?

Your explanation is highly appreciated,

Thanks,

Scott
 =20