[
https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563532#action_12563532
]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
All integration tests "imported" from microsling now pass, except the following
ones which are still marked with TODO_FAILS in the launchpad-webapp test code:
1) PostServletCreateTest.testCustomSavePrefixPlusPlus, a "++" save prefix does
not work, haven't checked if the cause is the test or the server-side code.
2) IncludeTest SLING-207 problem
3) testEspHtmlWithContentBasedPath, where scripts are located based on the
content path - not sure if we want to keep that feature.
4) Tests that use script languages other than javascript - we'll have to see
how we handle these, the best would be to test the scripting engines locally in
their own modules
5) All the SyntheticResourceTest, I haven't looked at those yet
6) The ujax client-side library is not included yet, find it under
http://svn.apache.org/repos/asf/incubator/sling/trunk/microsling/microsling-core/src/main/webapp/ujax
Apart from these points, we can now consider that the Launchpad works as
microsling-core did, but based on Sling code.
> Create the Sling Launchpad, based on microsling-core code
> ---------------------------------------------------------
>
> Key: SLING-149
> URL: https://issues.apache.org/jira/browse/SLING-149
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> Following up on the "[RT] Shall we merge microsling into Sling?" [1] and
> "µsling 2.0 requirements" [2] threads on sling-dev, we need to merge
> microsling into Sling.
> Here the are requirements as discussed in [2] (taking into account Felix's
> comment about WebDAV and Michael's comment about switching to other JCR
> repositories):
> µ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. µsling should ideally be
> delivered as a single runnable jar file.
> 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.
> [1] http://markmail.org/message/2s7agnu5kklti6da
> [2] http://markmail.org/message/atbjzjjp2wflkotb
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
