Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)
Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is comparatively easy (i.e. does not require a recompile) (I like CRX's Repository Explorer) -- Michael Marth, http://dev.day.com
Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)
Hi, Am Donnerstag, den 20.12.2007, 16:48 +0100 schrieb Michael Marth: Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is comparatively easy (i.e. does not require a recompile) (I like CRX's Repository Explorer) For those who don't know: CRX Repository Explorer is an addon to the commercial CRX product by Day, which is a Web interface comparable to Windows Explorer to explore the repository. Of course, nothing would provide Day from migrating the CRX Explorer to a Sling application :-) Regards Felix
Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)
On Dec 18, 2007 2:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote: ...Without going into the details, this means that usling is a pre-configured distribution of Sling. I'm wondering if we should stick with the name in this case?... Well, we could also try the webapp formerly known as µsling ;-) Seriously, I think we've been building some buzz about µsling in the last few months, and that has some value. So I'd keep the name even if it's just the module name of that default configuration. -Bertrand
Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)
sounds great. regards, david On 12/18/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote: Hi Wow, V2.0 already :-) We seem to agree on the need to merge µsling back into Sling, so I think it' be good to agree on the goals first - feel free to comment and expand on the following list of high-level goals and requirements for µsling 2.0. µsling 2.0 is a preconfigured instance of Sling, meant to allow web developers to test drive Sling by building scripted web and REST applications backed by a JCR repository. The µsling 2.0 distribution only requires a Java 5 VM to run, no installation is needed. Fifteen minutes should be enough to start µsling and understand the basic concepts, based on self-guiding examples. Java programming is not required to build web and REST applications with µsling 2.0: both server-side and client-side javascript code and presentation templates can be used to process HTTP requests. Other scripting and templating languages (JSP and BSF-supported ones) can be plugged in easily. The µjax application protocol and client-side javascript JCR proxy library make it easy to write powerful Ajaxish JCR-based applications with µsling 2.0. µsling 2.0 is built on the same codebase as Sling, it's only a specific configuration of Sling. All µsling 2.0 features are available in Sling applications, as long as they are enabled in the Sling configuration. Sling (and µsling, as it runs the same core code) uses OSGi to modularize the framework, but µsling does not require any OSGI skills, and makes OSGI largely invisible to beginners. All Sling features and modules can also be activated in a µsling 2.0 instance, by installing and activating the required OSGi bundles. µsling 2.0 passes all the integration tests of the existing microsling test suite (SVN revision 605206), with minor adaptations where needed. µsling 2.0 includes a WebDAV server module to make it easy to copy scripts into the JCR repository. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. -Bertrand
Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)
Hi, I can only support these ideas because they bring an entry-level Sling using a subset of the same components as are used in Sling. Am Dienstag, den 18.12.2007, 14:44 +0100 schrieb Bertrand Delacretaz: Wow, V2.0 already :-) Makes sense, as the initial Apache Sling release will also be 2.0. The µsling 2.0 distribution only requires a Java 5 VM to run, no installation is needed. Fifteen minutes should be enough to start µsling and understand the basic concepts, based on self-guiding examples. The Servlet Container is included, which makes it very easy to launch quickly. Deploying a web application into a servlet container, which you might have to get first, typically takes more than five minutes. Launching an executable jar file, typically takes less than a minute :-) ... µsling 2.0 includes a WebDAV server module to make it easy to copy scripts into the JCR repository. Absolutely. For this, I will create a WebDAV bundle from the existing Jackrabbit WebDAV support projects. AFAIK this is not resticted to Jackrabbit, though, but works on top of plain old JCR (if not, I'd like to be corrected) Regards Felix
