Ian- I'm not near a Sling working copy right now, but have you looked at using the NodeNameGenerator interface? I added it to solve a similar use case.
Justin On Jul 27, 2010, at 5:35 AM, Ian Boston <[email protected]> wrote: > Hi, > We have a requirement to store content based on a ID not on a path. I know > that this will violate aspects of David's model but the requirement is still > there and I have to support it. Details (for background reading only are at > [1] and [2]). > > I have an implementation that is close to working that uses a Filter to http > access to the underlying jcr storage and a ResourceProvider that does the > translation from http://localhost:8080/p/<ID> to jcr:/_p/hashPath(ID)/ID, > however we want to be able to > a) reuse all of the SlingEngine functionality and > b) upload files with a multipart post to /p where the file is stored as > /_p/hashPath(ID)/ID, where ID is generated > c) upload files with a multipart post to /p/ID where the file is stored as > /_p/hashPath(ID)/ID > > > For b, I can generate the ID and the file node, but AFAICT there is no way of > stopping the SlingFileUploadHelper from taking the name of the file from the > multipart post element and using it as the JCR path. > > I dont want to replicate the entire SlingPost infrastructure for this > operation, I would like either to make it possible to persuade the > SlingFileUploadHelper to use the resource path directly, or to hook in > another operation. > > Any ideas, > whats the best Sling way of achieving this without replicating code ? > > Ian > > 1 http://jira.sakaiproject.org/browse/KERN-891 > 2 > http://confluence.sakaiproject.org/display/KERNDOC/KERN-891+Pooled+Content+Service
