Opened 13 years ago

Closed 13 years ago

#1536 closed defect (fixed)

ModifiedDate not set when saving resources

Reported by: gBecker Owned by: jng
Priority: medium Milestone:
Component: Maestro Version: 2.2.0
Severity: major Keywords:
Cc: External ID:

Description

When saving any resources in Maestro the "ModifiedDate" is not updated. (Maestro v2.1.4.5245)

Open a resource in Maestro, change something and save the resource back to the repository. Then check "EnumerateResources" methode of wep api and see that the "ModifiedDate" hasn't changed!

Or check tooltip of the resource in the Maestro repository tree!

Change History (4)

comment:1 by gBecker, 13 years ago

Version: 2.1.02.2.0

comment:2 by jng, 13 years ago

When you save with Maestro it uses the COPYRESOURCE call to save the resource.

This is different from MG Studio, which uses the SETRESOURCE call to save the resource, and it correctly updates the modified date!

So the question is, shouldn't COPYRESOURCE do the same thing?

comment:3 by gBecker, 13 years ago

In my application I've created a custom "CacheDependency" for use with MapGuide resources. I store a xml representation of a MapDefinition in Cache and display a treeview of the Layers and LayerGroups in this MapDefinition. When the MapDefinition is modified in "MapGuide Studio" then the xml in Cache is removed (check ModifiedDate every 30 seconds). Next time a user access the webpage with the treeview, the xml of the changed MapDefinition is added into the cache again.

So I have to tell our customers that they have to use Studio for some special operations. But I would prefer them to use Maestro in most cases!

Changing a resource in Maestro means to me that the resource is modified. So the "ModifiedDate" has to be set correctly, even with COPYRESOURCE.

comment:4 by jng, 13 years ago

Resolution: fixed
Status: newclosed

Fixed r5426 (on the Maestro side at least)

Note: See TracTickets for help on using tickets.