#2 We have been using JCR with Magnolia since its inception, more than 5 years ago. Magnolia allows to plug in different repositories. The benefit here is less that you can replace Magnolia with another system while keeping the data. This would certainly be possible but only as an intermediate step. However, the ability to switch implementations to see what works best for your specific usage pattern is definitely assuring, and something we do regularly when updates are available. To that extend, I do hope to get my fingers on an Oracle Level 2 JCR eventually.

#2 test

#1 no

#1 bvm

#1 Great

#1 Great

#1 One of things i was going to use a JCR for was to store some Drools rules.

#1 Really glad to hear that!
And a hello to my old buddies who made the ranking possible!

- Juerg

#1 GREAT Things

#1 I'm just looking for access to fixed content repositories using jcr

#1 Want to get the white paper

#2 I think things may change with CQ5 seeing as it is built on top of Sling. With CQ4, I developed a separate application using Spring/JAX-RS to provide a set of content driven RESTful services. I then deployed it alongside CQ4 in the same application server. I just finished a Flex proof of concept that is driven entirely from these services. So, I guess your integration with CQ4 is more likely going to be at the repository level. However, with CQ5 you may have the option of integrating at a higher level. Also, we created a Flex/Flash component in CQ that we can use to actually embed the Flex applications right into ours.

- Shane

#1 We bought CQ5 and are also Flex developers...want to know more about how they can integrate.

#1 This discussion is so - typically and irrelevant. There is and there will never be the ultimate way to store and represent data. Most content data is hierarchical so that is where RDBMS do not match the needs of a developer. Unstructured data representing processes like car rental (as a classic example) are hard to store in a hierarchical way (or even impossible without breaking the hierarchical principle of relations).

Content should be stored in a hierarchical system while relational application data should be stored in a RDBMS. The challenge is the marriage of both architectures to complement each other.