Hi, On Fri, May 21, 2010 at 12:14 PM, Audrey Colbrant <[email protected]> wrote: > That was one of the links I gave below ;)...
Ah sorry, missed that. > ...I run Sling as a standalone application after packaging svn sources. > "Start Sling with the RMI export of the repository enabled. That’s standard > if you start the Sling launchpad/webapp module with mvn jetty:run, for > example. Sling can either run inside Tomcat, or standalone, as the connection > is made via RMI." > How to configure "RMI export of the repository" in the standalone version?... I think it's enabled by default, at least running java -jar target/org.apache.sling.launchpad-6-SNAPSHOT-standalone.jar -p 8888 starts listening on port 1099. > > ...Then, there is still the problem of integrating a *.war (those generated > for the JCR Explorer). > I didn't found how to do. At the moment I only have integrated *.jar bundles > from > Felix console.... You cannot add another war file to the Sling standalone server as there's no webapp container. That's why my blog post recommends using tomcat to host the jcr explorer war file, so if you follow that you should be able to start the jcr explorer, and if it's able to connect to the current Sling standalone server (I don't have time to check that right now) that should work. -Bertrand
