axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <stev...@iseran.com>
Subject Re: Removing "enum" for Tiger
Date Mon, 12 Jan 2004 10:37:41 GMT
Ias wrote:
> While Jakarta projects already resolved this issue, for example, from
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22343, I'd like to make a
> proposal on removing "enum" word for Tiger's the same reserved word. You
> can see some approach that Struts made at
> http://marc.theaimsgroup.com/?l=struts-dev&m=106070063517761&w=2 .
> 
> Here's collisions I found from Axis against Tiger.
> 
> package org.apache.axis.enum -> enum must not be used for a package name.
> local variable enum in QSMethodHandler -> enum must not be used for a local
> variable name.
> 
> I guess that renaming names of methods, fields and local variable is
> trivial, but refactoring package necessitates you to handle CVS carefully.
> 
> Thanks for your feedback in advance,
> 
> Ias

I did a run through this earlier, trying to clean up most things but 
leaving the .enum package alone as it was a more fundamental change.


The other issue is that there is an array of reserved words somewhere, 
that Axis uses when mapping from wsdl to java.

1. When enum is not in the list, axis can generate illegal java1.5 code

2. When enum is in the list, axis wont generate the same code as before


we know (2) as one of the tests no longer builds when enum is in the list.

Maybe for 1.2 we should add the notion of 'warn' keywords; have Axis 
warn on their presence. Or add a -language option to wsdl2java that 
controls which version of Java to target; 1.3, 1.4 or 1.5

-steve


Mime
View raw message