Hi, tung vu duc schrieb: > super!, it's exactly what i need. > > It's so cool how sling resolves the selection of the script to render > requested content. > > Do you plan to support .GSP und Groovy as scripting engine? I will be looking > forward to. :-D
We do not have a Groovy Scripting Engine in Sling yet. Adding it should not be a big issue, though: I assume you would just have to pick up the Groovy Library and Sun's ScriptEngine implementation for Groovy and create a bundle for inclusion in Sling. Problem is, though, that the ScriptEngines from the js223 project of dev.java.net are not available separately in a maven repository (yet). If you are able to build such a thing, we would be happy to add it to the Sling trunk or provide pointers whether to get it. Never heard about .GSP, is this "Groovy Server Pages" ? If someone more into the groovy world could help me out here, what would be required to support this, I would be open to add this, of course. Regards Felix > > Thanks you very much! > > > > ----- Original Message ---- > From: Torgeir Veimo <[EMAIL PROTECTED]> > To: [email protected] > Sent: Friday, September 5, 2008 1:07:27 PM > Subject: Re: How to beginn with Microsling > > > On 5 Sep 2008, at 20:48, tung vu duc wrote: > >> But i don't still understand how to beginn now. I have successful >> builded sling (the whole from trunk) with maven. what modules of >> whole sling should one need >> to have the functionaties of Microsling and how to integrate these >> with a Jackrabbit Repo. > > > You can take the resulting sling war file and put it into any web > container, eg tomcat. It contains the jackrabbit jars, and will > automatically set up a repository, which will be available instantly, > also via webdav. Then you can immediately put content and scripts into > sling using eg curl. > > Macintosh-3:sling torgeir$ find . -name "*.war" > ./launchpad/testing/target/org.apache.sling.launchpad.testing-4- > incubator-SNAPSHOT.war > ./launchpad/webapp/target/org.apache.sling.launchpad.webapp-4- > incubator-SNAPSHOT.war > > Use the bottom one, and rename it eg. sling.war before adding it to > tomcat. Your sling instance would then be available at > http://localhost:8080/sling/ > > Check eg with http://localhost:8080/sling/system/console/bundles or > try http://localhost:8080/sling/index.html > > I guess you've already read > http://incubator.apache.org/sling/site/discover-sling-in-15-minutes.html > ? >
