Can you at least describe me how it suppose to work? I mean when the session is created, how it correspond to the user, document and collaborator? In my scenario the annotation has just a content, creator name (user name) and the document to which it’s attached. I’m not sure how should I populate it. Can you share the Alfresco code? That would be really helpful I guess. Thanks.
Alfresco code unfortunately contains just a custom input handler sample which doesn’t work with 1.7 anyway. I’d really appreciate some sample to understand what and how needs to be implemented to store annotation in e.g. Alfresco or any custom (not db) location. Thanks.
Let me describe what I need:
- Session for now is per user-document pair.
- We are bound to this structure for a moment. This level of abstractions is needed.
- It’s made to give an additional flexibility in cases where some custom annotation handling will be requested.
- You can skip it or fill it with null values for now.
- This can be skipped also.
In my opinion the diagram should look more like on the attached screenshot. With that, we could create and keep the session in the HTTP session as it is volatile. User table is rather not required. All we need is the user name so we can read the user’s right to the document from the ECM system. Additionally document table is not required unless the DAO can replace the InputHandler, it would make much more sense then. All the integration in one place. Right now I have to implement two interfaces, one to return the content (InputHandler) and one just to return the file name, although I don’t know where that name is actually used:)