Upgrade Axis jar

[Diego Louzán <di...@metalicana.org>]

Currently Axis jar included in cvs is 1.2beta1. Since there some known problems 
with this jar with JDK1.5 (which prevent compiling WSRP4J cvs) due to the 
inclusion of the keyword "enum" in one of its packages, we should consider 
moving this jar version to one of the RCs Axis team released.

Regards.
Diego.

Re: Upgrade Axis jar

[Diego Louzán <di...@metalicana.org>]

I've been checking the code. The problem is only related to SwingConsumer it 
seems. The class org.apache.wsrp4j.util.MessageElementHelper uses 
org.apache.axis.encoding.SerializationContext interface and 
org.apache.axis.encoding.SerializationContextImpl classes from Axis. In Axis 
1.2RC there's only one (SerializationContext) which now is a concrete class. 
I've been able to compile on my machine, though I have not tested it yet (I 
don't use SwingConsumer). Anyway, this classes are not used at all, because 
org.apache.wsrp4j.consumer.app.driver.PropertyConsole has all its methods 
commented out.

Regards.
Diego.

Julie MacNaught wrote:
> There is an interface change in the next version of Axis which requires 
> a code change for us in MessageElementHelper.  There is not way to make 
> the change backward compatible, so we decided not to move up until Axis 
> releases.
> 
> Elliot Metsger wrote:
> 
>> I know that the axis team is moving forward and is working on cutting 
>> axis 1.2 final release.  I don't know the exact timetable, but it may 
>> be worth the wait.  I don't know how hard it would be to swap in the 
>> 1.2RC2 axis.jar and then switch later to the 1.2 final jar.
>>
>> Elliot
>>
>> Diego Louzán wrote:
>>
>>> Currently Axis jar included in cvs is 1.2beta1. Since there some 
>>> known problems with this jar with JDK1.5 (which prevent compiling 
>>> WSRP4J cvs) due to the inclusion of the keyword "enum" in one of its 
>>> packages, we should consider moving this jar version to one of the 
>>> RCs Axis team released.
>>>
>>> Regards.
>>> Diego.
>>
>>
>>
> 

Re: Upgrade Axis jar

[Julie MacNaught <jm...@apache.org>]

There is an interface change in the next version of Axis which requires 
a code change for us in MessageElementHelper.  There is not way to make 
the change backward compatible, so we decided not to move up until Axis 
releases.

Elliot Metsger wrote:

> I know that the axis team is moving forward and is working on cutting 
> axis 1.2 final release.  I don't know the exact timetable, but it may be 
> worth the wait.  I don't know how hard it would be to swap in the 1.2RC2 
> axis.jar and then switch later to the 1.2 final jar.
> 
> Elliot
> 
> Diego Louzán wrote:
> 
>> Currently Axis jar included in cvs is 1.2beta1. Since there some known 
>> problems with this jar with JDK1.5 (which prevent compiling WSRP4J 
>> cvs) due to the inclusion of the keyword "enum" in one of its 
>> packages, we should consider moving this jar version to one of the RCs 
>> Axis team released.
>>
>> Regards.
>> Diego.
> 
> 

-- 
Julie MacNaught
IBM Research
jmacna@apache.org
jmacna@us.ibm.com
DADB E3B5 8CB7 6B9B F4A0  8BF7 E830 1848 16A8 D3AB

Re: Upgrade Axis jar

[Elliot Metsger <em...@jhu.edu>]

I know that the axis team is moving forward and is working on cutting 
axis 1.2 final release.  I don't know the exact timetable, but it may be 
worth the wait.  I don't know how hard it would be to swap in the 1.2RC2 
axis.jar and then switch later to the 1.2 final jar.

Elliot

Diego Louzán wrote:
> Currently Axis jar included in cvs is 1.2beta1. Since there some known 
> problems with this jar with JDK1.5 (which prevent compiling WSRP4J cvs) 
> due to the inclusion of the keyword "enum" in one of its packages, we 
> should consider moving this jar version to one of the RCs Axis team 
> released.
> 
> Regards.
> Diego.