geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <d...@iq80.com>
Subject Re: New Feature Idea
Date Thu, 06 Apr 2006 18:59:38 GMT
Shouldn't update our QName implementation to be compatiable with 1.5?

Also, if we do ship with the XStream based configs on we no longer  
will have this problem.

-dain

On Apr 6, 2006, at 11:45 AM, Aaron Mulder wrote:

> I didn't think there were problems with web services in Geronimo in
> general between 1.4 and 1.5 -- I thought it's only the fact that
> QNames are serialized that causes problem.  I wouldn't expect to have
> a problem with an application that calls a web service or is called
> via a web service so long as it doesn't do any Java serialization
> involving QNames.  Is that not correct?  (Does Geronimo itself do the
> QName serialization for certain types of Web Services apps?)
>
> Thanks,
>      Aaron
>
> On 4/6/06, Matt Hogstrom <matt@hogstrom.org> wrote:
>> To be clear.  The reason DayTrader has an issue is that it uses  
>> WebServices and specifically it has
>> to do with the javax.xml.namespace.QName class has different  
>> serialization characteristics between
>> 1.4 and 1.5.  So, if someone wants to move back and forth between  
>> 1.4 and 1.5 and their using
>> WebServices they'll still have issues.
>>
>> Aaron Mulder wrote:
>>> We already support JDK 1.5 except for CORBA.  Because of the CORBA
>>> limitation Geronimo can't be certified on JDK 1.5, but if you leave
>>> CORBA disabled (and turn off the DayTrader sample application)
>>> Geronimo should run fine on 1.5.
>>>
>>> Thanks,
>>>     Aaron
>>>
>>> On 4/6/06, Christopher Stura <christophers@anthesi.it> wrote:
>>>
>>>> support for sun jdk 1.5
>>>>
>>>>
>>>
>>>
>>>
>>>
>>


Mime
View raw message