[Cosmo-dev] Problems subscribing to the Office Calendar

[Randy Letness]

Jared Rhine wrote:
> Would the workaround be removed after an ical4j fix makes it into 
> upstream (and we migrate to that new upstream)?  Is migration to an 
> unforked ical4j a 0.7 target?
>

Thats the plan.

> Do you already have a patch produced, Randy?  I assume it's a wrapper 
> around one place where Calendar.equals is used?  Is there only one 
> place Calendar.equals is called throughout the code?
>

I have fixed the code and added a unit test.  I'm just waiting for the 
go ahead to check into the 0.6 branch.  Instead of a wrapper, the fix 
involves updating the lastModified date of the stamp manually to let 
hibernate know its dirty.

> Randy, can we detect events that didn't get their stamp updated?  I'm 
> not sure if we can notify users or autofix any broken collections. 
> There's both the issues of fixing Cosmo (per this thread), and 
> mitigating the existing state of the service.
>

Yes, these are going to be any events with mis-matched contentLengths, 
and we can use a simple update query (listed in the defect) to fix.

> No data migration procedure will be used (since no schema changes will 
> hit 0.6.0.1).  I might even use the same Tomcat install and simply 
> update the Cosmo WAR (in-place/directory).

If we do a full release, we need to provide a simple migration of 
updating the version property in the server_properties table.

-Randy