Cool, I suspected as much, as this is all being done from some integration tests ( everything works fine when we start from using karaf ) I'll just add this my normal config bootstrap process.
-- Pull me down under... On Sat, Apr 10, 2010 at 1:31 AM, Justin Edelson <[email protected]> wrote: > Mark- > I don't know how this happened, but it should be easy to fix. > 1) Start Sling. > 2) Go to http://[sling host]:[sling port]/system/console/configMgr > 3) Find the "Apache Sling Embedded JCR Repository" configuration and > click Edit. > 4) Correct the values as necessary and click Save. > > Within the polling intveral you should be good to go. > > HTH, > Justin > > > > Justin > > On 4/8/10 9:02 PM, Mark Derricutt wrote: >> Looking further back up the call chain I see that the >> org.apache.sling.jcr.jackrabbit.server.SlingServerRepository component >> configuration has "" as the values for home and config, and its the >> when the File("").getParent() is called ( config ) that the NPE is >> called. >> >> I guess an earlier version of sling looked for the sling.home >> environment property which was being set in sling.properties of the >> old launchpad, and our integration tests? >> > >
