Looking at your site - seems like JSR 170 is a perfect fit for OpenEdit
because it's content based. In order to help you; however, it'd be nice
to know how far along you are with jackrabbit/jsr170 - and more
specifically what areas you're looking for help. Have you downloaded it
yet? Are you looking for node design collaboration?
In my mind - one thing missing from this community is collaboration on
common designs/best practices. I guess that's up to people like you and
I. But, I'd love to see mini-projects pop-up based on commonly used
designs ... things like a blogging framework.
Speaking of which, I spent last Friday writing a basic blogger based on
JSR 170 (model/node persistence). It works, but I'm not sure how much it
sucks. I'd really like to see a similar design from top to bottom (node
design, actual code, etc.) - to get an idea of how I'm doing.
-Robert
Chandresh Turakhia wrote:
Somehow Magnolia has been defacto :)
But templating is horrible in Mangnolia.
Also JLibrary now does the same.
I am planning to make OpenEdit ( www.openedit.org )
JCR compliants. Has anyone attempted the same. Any help in this
respect would be helpful.
I want to make OpenEdit talk to JSR 170 repository
Chand
----- Original Message ----- From: "Philipp Jurewicz"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Sunday, January 29, 2006 9:06 AM
Subject: Re: Advice on building a CMS
Hi
Maarten Volders wrote:
-I would like to build a web user interface that shows the tree
structure of the pages in my cms. But I do not want that all the
pages would be loaded immediately. But by using dwr / ajax I would
like to have async calls to my service layer and retrieve the pages
/ nodes I need only when opening a page in the tree structure. Has
anyone got experience with nodes in combination with dwr or ajax or
other async calls. Issues I should now or some advice on best
practices?
The Magnolia CMS builds upon Jackrabbit and they have a async tree
browser, but the don't use spring nor dwr.
