I've been down the path BTW Jason, fun may not be the best description ;-)
Granted this was about 4 years ago now so who knows what has changed. The
biggest problem I had, by far, was that the proprietary API I needed to use
was based on the assumption that it was dealing with JCR backed
Thought that would be the answer. I'll check out the prototype, thanks.
It'll be fun to write a ResourceProvider for this but it's going to have to go
to the bottom of my current list of things to get done in
Sling.
- Jason
On Wed, May 2, 2018, at 6:08 AM, Stefan Seifert wrote:
> hello
Hi Tobias,
Compatibility breaks happened with 0.x ->1.x and 1.x -> 2.x. Some are API
based, some about pipes themselves.
The major one I remember from top of my head is with sling query that, from 2.x
+ is much more used [0]. 1.x brought pipe builder (used in groovy creation you
talked about),
Hi together,
we decide on our project to use Sling Pipes for Content Migration. We are using
AEM 6.2, so we can only use Sling Pipes v0.0.10.
We are planning to build the pipes with groovy console on our local dev
machines in AEM 6.3. Unfortunately, the Sling Pipes created with v0.0.10 are
not
hello jason.
if you are using oak you might try the RDBDocumentStore [1] and RDBBlobStore
[2] implementation (i've never used them myself).
for using a lightweight approach accessing a RDBMS directly from a resource
provider the is no support currently afaik.
if you are looking for a generic
