I don't have an expertise in Nuxeo, so I don't know how to grant
access to those image resources without authentication, which I
thought could be an easy solution.
Anyway, if it doesn't work and If you need to deal with only small
size of icons and images from Nuxeo, then you might want to pursue
these instead:
- When user select an image resource in Nuxeo and when you are to save
the selection(s), you can store the binary data into
/content/gallery/${myhippoproject}/... by creating folders and nodes
in your specific rules (e.g,
/content/gallery/myhippoproject/dms/ca/fe/cafe-babe-....png*). You can
use JCR API to store the nodes, mimicking how Hippo default image
gallery nodes are stored.
- And, store the gallery image set node UUID into the document
property (instead of nuxeo url).
- Then, your image link generation will be the same as normal hippo
gallery image by using <@hst.link hippobean=document.dmsImage/> for
instance.
Another approach is, if the amount of images from Nuxeo is limited, to
use Hippo CMIS Replication forge module [1], which simply replicates
Nuxeo docs such as pdfs to hippo asset folder periodically. I haven't
tried with images, but images can be treated as an asset (without
thumbnail support in assets though) and so it can be generated to link
like above easily, too. But in this case, users need to select an
asset in hippo instead of Nuxeo directly.
So, it's up to you and depends on your requirements.
HTH,
Woonsan
[1]
http://cmisreplication.forge.onehippo.org/index.html