In one Ignite Chicago panel, Day’s own scientists and experts gathered to address any possible question about Day, JCR, CQ5, CRX and open development coming from the audience starving for answers. Here’s the scoop.
The panelists participating in the Q&A session included:
- Roy Fielding, Chief Scientist
- Greg Klebus, Sr. Product Manager
- Lars Trieloff, Product Manager
- Jean-Michel Pittet, SVP oF Engineering
- Gerd Hanke, Director of Product Management
Q: Is it possible to do group matching from an AD group to the same group in CQ? I cannot find this in documentation.
A: The functionality is there, we’ll look into making sure documentation is clear on this.
Q: What is the future of Day’s involvement in open development and open standards under Adobe?
A: We will keep doing what we are doing right now, addressed the questionRoy Fielding. We will continue using OSGi and open development anddesign, continuing to be on the leading edge of server-side OSGi.
Daywill continue being a part of the Apache Software Foundation (ASF).Adobe is, actually, looking to learn from Day in this field, we justneed to figure out how to do that. Adobe is a big company, but we’re agood match and just need to figure out how to improve both companies.
Regardingthe future of open standards outside of Day, what I tell people is thatI am lousy at making predictions, but good at making everyone do what Iwant them to do. Right now, I am working on Waka – a protocol for HTTPreplacement. I just need to publish it before the acquisition closes in 2weeks [laughs].
HTML5 is a big huha in standards. It’s a great openstandard. The problem though is that it is a browser developmentstandard, and not even browsers agree with what’s in it. Calling HTML5 astandard right now is a joke, really. It will take a year or two forthat to shake out.
Q: How do you get involved in open development?
Fieldinganswered with his personal story on how he got into the open standardsfield. He was paid to do research and had freedom to write about webtechnology. As a result, he wrote about something that became aworldwide standard [HTTP].
Other panelists added their suggestionsand recommended communicating on ASF mailing lists as one of the ways toget involved. Within W3C, it is a little more complicated to getinvolved, but possible. Another way is if you have an idea, find anexisting project or standard and ask the participants and committers ofthat project directly on how to get involved. Maybe there’s an extensionwaiting to materialize.
Q: Are there any plans to move from jsp to jsf?
A:CQ5 was built to support flexibility in the choice of frameworks. Eventhough the product ships mainly in jsp, it also includes examples ofother technologies. The goal is to give customers the most flexibilityif they have already made investments into existing infrastructures. JSFhas a lot more session-oriented interactions, and Day usually tries tosteer away from session-centric development and go towards RESTfulinteractions vs. the heavy session-based interaction.
Q: Do we keep legacy, Spring MVC work or replace it with Day?
Fieldingagain chimed in with a tongue-in-cheek comment: Replace everything, butI say that because I don’t have production responsibilities.
Thedeal is with a lot of migrations and different layers of architecture isto turn to the REST paradigm – you can wrap all apps with new apps anduse them as a data source. JCR has same principles.
But still, thisis never an easy process. Different ways exist as to how to use CQ5:either to manage content directly from it, or can use one of your ownapps to retrieve content from CQ instead.
It becomes a businesstrade-off: how well can you solve your business issues with one or theother technology and what are the benefits (Do you want drag-and-drop?
Q: What are some of the biggest challenges of Day’s dev team?
A:We used to have a marketing challenge (explaining to the market what wehad built). But we are lucky that Eric [Hansen] and Kevin [Cochrane]have joined the team. Plus, a combination of things in the industry, anopportunity to be in the right place at the right time when we came outwith CQ5. That was a 10-year effort.
CQ4 had a repository, but not the app. In CQ5, you can see the great architecture.
Q: Why do you manage images in CQ in a DAM folder and pages outside of that folder?
A:By design, there are different locations for storing pages and assets.Users are used to having definite locations for storing, structuring andorganizing sites, pages, languages. And all assets (and theirrenditions) go into their own structure. It is more about findabilityand content management.
Q: What do you think about the future of RDF and semantic web?
A:Nothing to do with technology, but semantic web is based on idea ofwrapping all logic with RDF metadata to start using global web as aknowledge base. The problem here is around how people use the web, howthey make links, the actual semantic uses of the web. RDF says only onemeaning for a URI, but the same picture of a beach can be interpretedfrom many semantical perspectives.
Web is a messy place. RDF andsemantic web is two-fold: web society on one side and mathematicians onthe other side. These two views of the world are not compatible.Eventually, they [the latter] will get tired of trying to change theworld.
Q: What is the future of CRX persistence? Will the new persistence technologies like CouchDB, Cassandra, etc. used in the persistence layer?
A: [Submitted by Greg Klebus] The Apache Jackrabbit team (Jackrabbit provides the core repository implementation in CRX) has been working on the new repository architecture for the next major release (Jackrabbit 3). The final architecture hasn't been decided yet, and the community still keeps the options open as to which persistence technologies to support in the persistence layer. The RDBMS databases (supported now) as well as these new persistence technologies (CouchDB, Cassandra, etc) are considered.
Day developers -- being the major contributors to Apache Jackrabbit -- have been leading this discussion.
Secondly, Day CRX has its own scalable file-system-based TarPM persistence technology. From the CRX & CQ5 product perspective this will be an additional persistence option on top of those supported by Apache Jackrabbit.
From the architectural standpoint the most important questions to be asked before settling down on a specific set of persistence models for CRX 3 (and Jackrabbit 3) are:
- From the architecture standpoint: What are the goals of the new persistence model? What characteristics are we focusing on and what tradeoffs will we accept
- From the product standpoint: What are the needs persistence/deployment needs of the majority of applications running on CRX?
Everyone interested in shaping the future of JCR persistence in CRX, CQ5 and Jackrabbit is invited to follow discussions on the Apache Jackrabbit mailing lists, and to contribute ideas and feedback.