[FYI] build result with Tiger

[Ias <ia...@tmax.co.kr>]

Hi all,

With the first public release of J2SE 1.5 codenamed Tiger, I built Axis and
got the result attached to this message. I ran "ant clean compile" and it
actually failed with no wonder. The main reasons are

1. newly introduced "enum" keyword
2. JAXP 1.3's DOM level 3 interfaces

I hope to resolve enum issue first and next take a look at JAXP 1.3's
changes.

Any thought?

Ias

=========================================================
Lee, Changshin (Korean name)
Ias (International name)
               Company Web Site: http://www.tmax.co.kr
               Personal Web Site: http://www.iasandcb.pe.kr
---------------------------------------------------------
JSR 201, 204, 222 and 224 EG member
Apache Axis (JAX-RPC and SAAJ) and JaxMe (JAXB) committer
R&D Center
Tmax Soft, Inc.
=========================================================

Re: [FYI] build result with Tiger

[Sanjiva Weerawarana <sa...@watson.ibm.com>]

"Steve Loughran" <st...@iseran.com> writes:
> 
> And that is the big question really: when does the change go in?
> 
> -steve

I'd say Tiger support would be Axis 2.0 timeframe .. even if Tiger
is shipping a real 1.0 it takes some time to get usage. At this 
points its only a beta and IMO major Axis changes should not be done
to support such a beast. 

Sanjiva.

Re: [FYI] build result with Tiger

[Steve Loughran <st...@iseran.com>]

Ias wrote:
> Hi all,
> 
> With the first public release of J2SE 1.5 codenamed Tiger, I built Axis and
> got the result attached to this message. I ran "ant clean compile" and it
> actually failed with no wonder. The main reasons are
> 
> 1. newly introduced "enum" keyword
> 2. JAXP 1.3's DOM level 3 interfaces
> 
> I hope to resolve enum issue first and next take a look at JAXP 1.3's
> changes.

Enum is going to be trouble. As well as moving the entire package (which 
may brake existing code), you need to add enum to the list of reserved 
words that WSDL knows about when naming things. Which will also break 
anything that imports WSDL where enum came out as a method, field, etc.

That does not mean that we cannot do it, just that it needs to be 
documented as a 'known incompatibility between Axis 1.1 and 1.2' (or 1.2 
and 1.3, depending on where the change goes)

And that is the big question really: when does the change go in?

-steve