Hi Wolf, thanks for the feedback. I preferred to use plain dojo javascript because I like the dojo framework and I didn't find as many components in myfaces as I found in dojo. For the moment I don't think I'll move the project to JSF because the contrib project is almost finished[1], but I'm open to other ideas in case someone volunteers to make most of the development effort :).
br, edgar See the demo at http://edgarpoce.dyndns.org:8080/jcr-browser/browser/. On 11/20/06, Wolf Benz <[EMAIL PROTECTED]> wrote:
This is a great idea! Some thoughts, fro the top of my head: - do we really need AJAX/Dojo, or could plain (MyFaces) components be used (thus shifting the AJAX to MyFaces components that use it - would speed up thsi development) They have some very cool components. (also check their sandbox) It would also imply other devs could quicker jump on the development boat (less require techs) As plain JSF is the standard now, I think it would also get much quicker to a critical mass adoption. (usage) The JCR-taglib will be usable as is in the JSF pages. On the "servlet": I'd like to encourage you to use a "Servlet Filter" instead. Makes it more modular. (to e.g. work in combination with JSF - for which the JSF Servlet is required. Using a servlet would make the combination of your code with JSF impossible, beforehand...) That would be terrible! ;-) The idea of a contrib project is great. As JCR is a rising star, this will be a very much appreciated addition. What value have all these data if you can't make it smile in a screen? Buy, Wolf ____________ -- View this message in context: http://www.nabble.com/web-based-jcr-browser-contribution-tf2551645.html#a7442691 Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.
