Expiring Content after deploy with FSR

[unknown-user]

I have 3.2r running and we are using Alfresco WCM in a slightly less traditional way.  We are using the FSR to deploy the content to an XSAN repository that is read from by Endeca and WebSphere Commerce to retrieve the content.  Launching the content works fine as it is still in Alfresco at this time.  Once the FSR moves it to an external file store, how, if at all, would you expire it.  Is the WCM functionality supposed to use the FSR to locate and remove content when it is no longer valid, or is the expire only meant to work if the content is running traditionally from the Alfresco WCM via the virtualization server?

[mrogers]

You would need some sort of scheduled job running on your authoring environment to "expire it".

If you have copied content out of the standalone deployment server's  control then you either need to replace the entire file set on your destination or hook into one of the FSR's callback to delete a file.    

Or you implement your own deployment target and provide an implemetation of the delete method.