You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/01/07 15:30:35 UTC
[jira] Created: (SLING-149) Merge microsling into Sling
Merge microsling into Sling
---------------------------
Key: SLING-149
URL: https://issues.apache.org/jira/browse/SLING-149
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: 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.
[jira] Commented: (SLING-149) Merge microsling into Sling
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556619#action_12556619 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
I have created a skeleton at http://svn.apache.org/repos/asf/incubator/sling/trunk/usling/usling-webapp
With revision 609682, "mvn clean package jetty:run" starts Jetty with the Sling management console available at http://localhost:8080/sling
> Merge microsling into Sling
> ---------------------------
>
> Key: SLING-149
> URL: https://issues.apache.org/jira/browse/SLING-149
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: 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.
[jira] Closed: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-149.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Apart for a small number of integration tests this integration may well be assumed complete. Therefore I close this issue for now.
> 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
> Fix For: 2.0.0
>
>
> 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.
[jira] Commented: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560994#action_12560994 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
Moved the http://svn.apache.org/repos/asf/incubator/sling/trunk/usling/ code to http://svn.apache.org/repos/asf/incubator/sling/trunk/launchpad/
> 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.
[jira] Assigned: (SLING-149) Merge microsling into Sling
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz reassigned SLING-149:
-----------------------------------------
Assignee: Bertrand Delacretaz
> Merge microsling into Sling
> ---------------------------
>
> 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.
[jira] Commented: (SLING-149) Merge microsling into Sling
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556831#action_12556831 ]
Felix Meschberger commented on SLING-149:
-----------------------------------------
> µsling 2.0 includes a WebDAV server module to make it easy to copy
> scripts into the JCR repository.
I created SLING-150 to track the creation of a WebDAV bundle.
> Merge microsling into Sling
> ---------------------------
>
> 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.
[jira] Commented: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563524#action_12563524 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
Getting started docs created at http://cwiki.apache.org/confluence/display/SLING/Discover+Sling+in+15+minutes
> 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.
[jira] Commented: (SLING-149) Merge microsling into Sling
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12558629#action_12558629 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
usling-webapp now implements (at least partly) the ujax POST "protocol", and usling default rendering.
See http://svn.apache.org/repos/asf/incubator/sling/trunk/usling/usling-webapp/README.txt
> Merge microsling into Sling
> ---------------------------
>
> 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.
[jira] Commented: (SLING-149) Merge microsling into Sling
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556896#action_12556896 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
I have created http://svn.apache.org/repos/asf/incubator/sling/trunk/usling/usling-servlets/ to hold the µsling servlets - for now that module contains only a do-nothing servlet, that is loaded automatically as a bundle in the usling-webapp module.
> Merge microsling into Sling
> ---------------------------
>
> 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.
[jira] Commented: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571316#action_12571316 ]
Felix Meschberger commented on SLING-149:
-----------------------------------------
If the test relevant concepts not handled by other tests, they should probably be migrated to JavaScript.
Otherwise +1 for removal
> 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.
[jira] Updated: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz updated SLING-149:
--------------------------------------
Summary: Create the Sling Launchpad, based on microsling-core code (was: Merge microsling into Sling)
As discussed on the sling-dev list, the end result of this will be named "the Sling Launchpad" to make it clear that there's only one "product".
Here's the suggested marketing blurb, which completes the above requirements:
he Sling Launchpad is a ready-to-run Sling configuration, providing
an embedded JCR content repository and web server, a selection of
Sling components, and documentation and examples. The Launchpad makes
it easy to get started with Sling and to develop script-based
applications.
Fifteen minutes should be enough to get started with Sling using the
Launchpad, yet the full functionality of Sling is available by loading
additional Sling (or custom) OSGi modules as needed, using Sling's
web-based OSGi management console.
> 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.
Re: microsling
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Jan 15, 2008 3:41 PM, paksegu <pa...@yahoo.com> wrote:
> ...Is usling bundled with ujax?...
Yes, if you start using "mvn clean jetty:run" in the microsling-core
module [1], you'll have ujax.
This is not working yet in the usling/usling-webapp module, I'm working on that.
-Bertrand
[1] http://svn.apache.org/repos/asf/incubator/sling/trunk/microsling/microsling-core/
microsling
Posted by paksegu <pa...@yahoo.com>.
Is usling bundled with ujax?
Ransford Segu-Baffoe
paksegu@yahoo.com
https://serenade.dev.java.net/
http://www.noqturnalmediasystems.com/
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
[jira] Commented: (SLING-149) Merge microsling into Sling
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559010#action_12559010 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
The maven-cargo-plugin integration test setup is ready, I'll start moving the microsling tests under usling-webapp/src/test/java/org/apache/sling/usling/webapp/integrationtest
> Merge microsling into Sling
> ---------------------------
>
> 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.
[jira] Commented: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571308#action_12571308 ]
Bertrand Delacretaz commented on SLING-149:
-------------------------------------------
The vast majority of the microsling integration tests now pass, with those test classes still containing some tests disabled with TODO_FAILS:
integrationtest/IncludeTest.java
integrationtest/NodetypeRenderingTest.java
integrationtest/SlingResourceTypeRenderingTest.java
integrationtest/SyntheticResourceTest.java
integrationtest/ujax/PostServletCreateTest.java
Most of the failing tests are related to scripting languages that are not included by default in the Launchpad (Velocity, Ruby, FreeMarker) - I don't think we want to bloat the Launchpad too much, so I'll probably just remove those tests.
> 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.
[jira] Commented: (SLING-149) Create the Sling Launchpad, based on
microsling-core code
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ 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.