axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <gdani...@macromedia.com>
Subject RE: Changing JAX-RPC interfaces - philosophical question
Date Wed, 27 Mar 2002 18:48:22 GMT
Ya, mon.  +1 to taking the hit now.

-----Original Message-----
From: Volkmann, Mark [mailto:Mark.Volkmann@AGEDWARDS.com]
Sent: Wednesday, March 27, 2002 9:31 AM
To: 'axis-dev@xml.apache.org'
Subject: RE: Changing JAX-RPC interfaces - philosophical question



I don't think there is too much suffering involved in correcting constant references. I'm
not an Axis developer, I'm an Axis user. I'd prefer to get things right during the beta process
and not leave incorrect remnants behind when the first non-beta release hits. I vote for option
#1.

> -----Original Message----- 
> From: Russell Butek [ mailto:butek@us.ibm.com <mailto:butek@us.ibm.com> ] 
> Sent: Wednesday, March 27, 2002 7:56 AM 
> To: axis-dev@xml.apache.org 
> Subject: Changing JAX-RPC interfaces - philosophical question 
> 
> 
> There are some changes in the JAX-RPC spec that will affect 
> users.  For 
> example, javax.xml.rpc.ParameterMode.PARAM_MODE_IN has changed to 
> javax.xml.rpc.ParameterMode.IN.  We can do one of two things here: 
> 
> 1.  Make the change and let users suffer (we ARE in beta, after all) 
> 2.  Provide both and deprecate the old one for one release - 
> through beta 2 
> - and get rid of it in the next - beta3.  This process isn't always 
> possible (for example:  old:  "public void method() throws X"; new: 
> "public int method() throws Y"), but I don't think the impossible 
> situations should exist at this point in the spec's life. 
> 
> I would assume folks would prefer that I do #2, but I thought I'd ask. 
> 
> Russell Butek 
> butek@us.ibm.com 
> 



***************************************************************************************
WARNING: All e-mail sent to and from this address will be received or
otherwise recorded by the A.G. Edwards corporate e-mail system and is
subject to archival, monitoring or review by, and/or disclosure to,
someone other than the recipient.
***************************************************************************************



Mime
View raw message