sakaiproject/nakamura — pull request #638 by zathomas (2012-03-06 21:43:24+00:00)
Title: Fix the output from the request where migrations happen

These two commits address the problem of migrated content not coming back fully in the request where the migration occurs.

This was happening in both the pooled content migrations and pubspace/privspace migrations, but for two different reasons.

In the former, the problem was that the migrator handed back a `Content` object that had been created in an administrative session. The non-admin session using that content to write the output to the response could not descend to the child nodes.

In the latter case (using the servlet filter) we needed to switch to a non-Sling filter, so that resource resolution won't have already happened by the time we reach the filter. What was happening was that the migration was executing successfully, but the request already had a handle to the _old_ content by that point, so we weren't seeing the changes in the output.