Hi Bertrand, Thanks for the followup - we've since traced the problem down to being paxweb 0.5.1 itself and not sling. We've raised a ticket over at OPS4J and the issue is scheduled for a 0.5.2 release:
http://issues.ops4j.org/jira/browse/PAXWEB-108 Mark On Wed, Nov 12, 2008 at 12:31 AM, Bertrand Delacretaz < [EMAIL PROTECTED]> wrote: > Hi Mark, > > Going through my mail backlog I notice that we haven't replied to your > question, is that still current? > > If yes it might be safer to create a JIRA issue so that doesn't fall > into the cracks - apparently none of us had an answer off the top of > their head. > > -Bertrand > > On Sun, Oct 19, 2008 at 11:55 PM, Mark Derricutt <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > We recently updated our sling based application (based around the > > sling-launchpad osgi deployer) to use pax-web-server 0.5.1 (which uses > NIO) > > and have noticed that for some reason none of sling content gets returned > > anymore, instead we see: > > > > ** Node dumped by StreamRendererServlet** > > Node path:/ > > Resource metadata: {sling.resolutionPath=/} > > > > ** Node properties ** > > jcr:primaryType: rep:root > > > > > > being output to the browser. Is this a known issue or something new? Is > > there anything I can look at to try and diagnose whats going on? > > > > Mark > > > > -- > > "It is easier to optimize correct code than to correct optimized code." > -- > > Bill Harlan > > > -- "It is easier to optimize correct code than to correct optimized code." -- Bill Harlan
