[AG-TECH] Backwards compatibility bug AG3.1 -> AG3.0.2?

[Thomas D. Uram]

Hi Michael:

I ran across this problem last week also.  The problem arises when the 
RemoveData method tries to send the RemoveData event.  The removal 
actually succeeds, but users do not receive the associated event, and 
the removing user is informed of the failure.  Because this happens on 
the server, it will only be fixed by server upgrades.  I have fixed it 
in the server for the upcoming 3.1 release.

Tom


More detail for those interested:
The Venue.RemoveData method takes a deserialized DataDescription and 
tries to serialize it again when sending the RemoveData event, but ZSI 
has added attributes to the DataDescription which cause serialization to 
fail.  This is fixed in 3.1 by creating a clean DataDescription on the 
server side and sending it out instead.  This problem will arise in 
other cases where the server tries to serialize an incoming object; 
we'll scrub the code to look for other instances of the problem.


On 12/19/07 7:44 AM, Michael Braitmaier wrote:
> Hello everyone!
>
> I recently tried to setup mixed operation of AG3.1 and AG3.0.2 where 
> the server was running on AG3.0.2 and
> clients where running partially on AG3.0.2 and AG3.1. The problems I 
> encountered occured with removal of files from the data store
> with AG3.1 clients as well as removal of SharedApplications from the 
> server with AG3.1 clients. The appropriate log excerpts
> are attched in the two text files. Furthermore startup of 
> SharedApplications don't seem to work however I couldn't find out
> the problem so far, as no exception is thrown.
>
> I think the removal issues are bugs with backwards compatibility (I am 
> sure of it with the file removal, not so sure with SharedApplication 
> removal)
>
> I used the latest CVS code checked-out today at noon CET.
>
> Best Regards
> Michael