[
https://issues.apache.org/jira/browse/SLING-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-2225.
--------------------------------------
Resolution: Fixed
A few more fixes and finetuning applied.
Plus added documentation ("Embedding the Standalone Java Application") to the
Sling Site page http://sling.apache.org/site/embedding-sling.html
> Improve support for embedding the Sling Launcher in Java applications
> ---------------------------------------------------------------------
>
> Key: SLING-2225
> URL: https://issues.apache.org/jira/browse/SLING-2225
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.3.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: Launchpad Base 2.4.0
>
>
> The only way to embed the Sling launcher today is to build an array of
> command line options and call the static Main.main(String[] args) method from
> the application. This is kind of weird and only allows a small subset of
> configuration properties to be easily supplied by the calling application.
> In addition the handling of command line options is currently split between
> the Main and the MainDelagate class: The Main class implements the usage
> functionality (for the -h command line option) while the MainDelegate class
> implements the actual conversion of command line options to internal
> configuration property. This should be improved in that the support for real
> command lines should be consolidated in the Main class and the map of
> configuration properties supplied to the MainDelagate class should only
> contain actual configuration properties.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
