- Andrew Kos
- Bill Burlein
- Bryan Williams
- Christian Vozar
- Jeff Brown
- John Kraus
- Joseph Mak
- Josh Durbin
- Mark Daugherty
- Matt Van Bergen
- Melissa Geoffrion
- Michael Kang
- Michael Chan
- Michael Hodgdon
- Mike Motherway
- Molly McDaniel
- Nadia Maciulis
- Pat McLoughlin
- Paul Michelotti
- Puru Hemnani
- Rohit Srinath
- Ryan Lunka
- Tom Kelly
All Blogs
CITYTECH Blogroll:
Archive for September 2010
Merging Day CQ5, Spring, and JPA for a hybrid web application
September 13, 2010 7:25 PM
If you subscribe to the mantra that “everything is content” then you probably can store everything in CQ and never have a need to integrate with other data-oriented systems. On the other hand, if your organization or client deals with assets such as relational databases, CRMs, or other systems, your job is probably more interesting and you may want to read on. What we have seen is that there is a growing demand to integrate the power of a full-fledged WCM, such as Day CQ5, with functionality previously found only in traditional transactional-based web applications. These hybrid applications must render a web page that integrates both author-controlled content and traditional enterprise data, sourced from assets such as Oracle DB, SAP, Salesforce, etc. They must also be capable of handling business transactions typically done on the web.
Recent Posts
- Descriptive JMX Beans in AEM/CQ
- Invisible requirements within Business requirements
- Building a better Options Predicate
- Javascript, This, and You.
- Extensionless URLs with Adobe Experience Manager
- The Life of a Tester in Adobe CQ World!
- Limitations of the CQ Parsys Model and the Implementation of a Nested Paragraph System
- Google Analytics and AEM: No JavaScript? No Problem.
- Using Apache FOP to generate a PDF document based on a form submission data
- Configuring SAML in AEM 5.6