Hi
I'm one of the developer of the here named magnolia and would like to
give you some hints.
The Magnolia CMS builds upon Jackrabbit and they have a async tree
browser, but the don't use spring nor dwr.
This is true for the current version (the server side code generates
HTML snippets which are placed on the client side). As you can
imagine this is not how it should be, because other not HTML clients
are blocked. Never else if you like this approach (because it is
simple) have a look at the prototype.js which gives you a lot of
methods to do that without DWR or other additional stuff. You pass a
url and name the dive where the result should get placed. Good to
know that prototype.js is the base code of a lot of other AJAX
frameworks.
The magnolia dev team decided to use Spring and DWR in the future
versions, since this makes totally sense.
About your question. An async Tree should not be something depending
on JCR since this is a common GUI Control. The MyFaces Tomahawk
project is working in that direction for example. I note here shortly
what we will do in the future to give you some hints:
- DWR is used to call the model (different implementations possible,
the most famous will be the JCR one)
- DWR returns only data and the actions attached to the node (no HTML)
- each node can define its Context Menu (actions)
- Rendering on the client side (this makes it ease to use the service
classes for SOAP too)
- Rendering by trimpaths template.js (like FreeMarker but for JS).
This avoids to have the HTML code spread around the JS code (you
place the templates in divs).
- The initial call goes to a JSP (or what ever) providing all the
needed rendering Templates (each in one named div)
This splitts the rendering (Client, JSP) and the model (DWR, SOAP,
POJOS) completely.
Hope this helped
Regards,
Philipp Bracher
obinary ltd.
-----------------------------------------------------
[EMAIL PROTECTED] http://obinary.com
magnolia content management http://magnolia.info
-----------------------------------------------------
