Hi,
On Wed, 2017-04-12 at 15:31 +, Beaudet, David wrote:
> Thanks Roy, yes that's the other suggestion Adobe had identified and
> we're looking at it as well. In your opinion is integration of DAM
> Assets at the JCR level with Oak just a bad idea even if it is
> possible?
With the
hi david, long-time AEM developer here. i wouldn't recommend grafting at
oak level even if it was possible. the resource API of sling is loose
and amenable to all sorts of datatypes. and since your main point of
interaction is through sling/AEM, that would be the easiest to build out
and
Thanks Roy, yes that's the other suggestion Adobe had identified and we're
looking at it as well. In your opinion is integration of DAM Assets at the JCR
level with Oak just a bad idea even if it is possible?
From: Roy Teeuwen [mailto:r...@teeuwen.be]
Sent: Wednesday, April 12, 2017 11:22 AM
Hey David,
Seeing as you are using AEM, thus Sling, have you looked at the
ResourceProvider interface? With this you can bind resources coming from
another place than the JCR repo to the content tree.
You can look at these examples, the first one fetches content from a couchbase,
the second
