encoding.XMLType -- Note that it 'extends Constants', so it picks up the
newly defined constants under the new name... turns out there is only a
single reference to an XMLType.attribute, and that is the only field unique
to XMLType: AXIS_VOID.
For AXIS users, Rich has indicated that we should consider moving some
attributes from Constants to XMLType. I'll take that as a second step in
the future.
It's passing tests, so here it comes...
<ras>
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
Tom Jordahl
<tomj@macromedia To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
.com> cc:
Subject: RE: [axis] : Code change
across the board
05/29/2002 04:55
PM
Please respond
to axis-dev
+1
Changes look OK to me.
This may break users, especially the encoding.XMLType changes. That makes
me nervous, but I am -0 to it. Can we deprecate the constants?
--
Tom Jordahl
Macromedia
-----Original Message-----
From: Richard Sitze [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 29, 2002 5:16 PM
To: [EMAIL PROTECTED]
Subject: Re: [axis] : Code change across the board
It's been suggested that I submit for review the "new" Constants,
WSDDConstants, and XMLType files before I commit them (and corresponding
changes to many other files):
(See attached file: Constants.java)
(See attached file: WSDDConstants.java)
(See attached file: XMLType.java)
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
