Hi Mike, Mike Müller schrieb: > Hi Bertrand, hi Pontus > > Thanks very much for your suggestions. I tried the remote debugging way and > it worked well. > I'm wondering a little bit, that the best open source thing which is > available today to explore a jcr is the mentioned JCR Explorer which feels > very basic and isn't any more under development. Maybe that's one of the > reasons why JCR isn't taking the world by storm... - but yes, it worked. > When searching the sling mailing list I read a lot of entries proposing a > tool to explore JCR. Are there any efforts at the time to build a better > explorer or do someone know from such a project being developed outside the > sling community? > My feeling is, that a good explorer is something very important to get a > broad community building complex apps with a JCR based framework like sling.
Agreed from the depth of my heart -- and having a good explorer in Sling would be a good thing, though I think Sling should really to a Resource Explorer (which not just renders the repository Items but also resources from ResourceProviders such as the Bundle resource provider or the file system resource provider. If you want to have something quickly, you might consider looking at the CRX Feature for Eclipse, which is available for free from http://www.day.com/eclipse/ (not open-source, though). Hope this helps. Regards Felix > > best regards > mike > >> I use remote debugging, starting Sling from the command-line >> with options like >> >> java -Xmx384M -Xdebug -Xnoagent -Djava.compiler=NONE >> -Xrunjdwp:transport=dt_socket,address=30303,server=y,suspend=n >> ... >> >> And connect from Eclipse using a remote debugging session. There might >> be more integrated ways, but that works for me. >> >> To update Sling bundles, I use the -P autoInstallBundle maven profile >> defined in parent/pom.xml. >> >> Until we have a better solution, the JCR Explorer can help, I have >> written a post on my blog [1] about how to connect it with Sling.
