Sorry, Karen, I thought I mentioned in an earlier post that the fix -- and the new naming scheme -- hasn't been committed to trunk yet. There are still some outstanding tests, but I'll most probably finish them tomorrow.
Christoph Am 01.10.2012 um 18:08 schrieb Karen Dolan <[email protected]>: > Christoph, > > (MediaInspectionServiceImpl:440) "Element > /Users/ced/dev/matterhorn/versions/trunk-1.4.x/felix/work/opencast/workspace/http_localhost_8080/episode/archive/mediapackage/4903882c-c76e-4353-8aa0-3afffd7acaa4/track-1/2 > has no file extension". > > Do you really have a file named "2.mp4", or similar, somewhere on your > server, or is the log message just misleading? > > - Karen > > On 10/1/2012 11:48 AM, Christoph E. Driessen (Issue Comment Edited) (JIRA) > wrote: >> [ >> http://opencast.jira.com/browse/MH-9215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31859#comment-31859 >> ] >> >> Christoph E. Driessen edited comment on MH-9215 at 10/1/12 3:47 PM: >> -------------------------------------------------------------------- >> >> No certainly do agnostic URLs not require a file extension. This is in fact >> a compromise: MH components like the MediaInspectionService or the WorkSpace >> are _not_ agnostic to URLs and require a file extension. Removing this fact >> is a major refactoring not easy to implement. Side effects may occur leading >> to even more refactorings. To conclude: This is right now the easiest and >> fastest solution. >> >> To answer your second question: The URNs won't be touched. They stay as they >> are. The extension will be applied dynamically by the episode service REST >> endpoint on delivery of a media package according to the following schema >> >> http://{host}/episode/archive/mediapackage/{mediaPackageId}/{mediaPackageElementId}/{version}/{type}.{fileSuffixOfMimeType} >> >> was (Author: cedriessen): >> No certainly do agnostic URLs not require a file extension. This is in >> fact a compromise: MH components like the MediaInspectionService or the >> WorkSpace are _not_ agnostic to URLs and require a file extension. Removing >> this fact is a major refactoring not easy to implement with possible side >> effects. To conclude: This is right now the easiest and fastest solution. >> >> To answer your second question: The URNs won't be touched. They stay as they >> are. The extension will be applied dynamically by the episode service REST >> endpoint on delivery of a media package according to the following schema >> >> http://{host}/episode/archive/mediapackage/{mediaPackageId}/{mediaPackageElementId}/{version}/{type}.{fileSuffixOfMimeType} >> >> > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
