Tested now with sling trunk and I did not find any problems. I replaced pax-web-service (0.6.0) bundle with org.apache.felix.http.jetty (2.0.2) in launchpad/app/pom.xml and compiled launchpad/app. Ran the standalone version and did not see any problems.
BR, Sten Roger Sandvik On Tue, Oct 6, 2009 at 10:49 AM, Mark Derricutt <[email protected]> wrote: > It was org.apache.felix.http.jetty 2.0.2 and sling 2.0.2-incubator (started > using the launchpad ). > > -- > Pull me down under... > > On Tue, Oct 6, 2009 at 7:36 PM, Sten Roger Sandvik <[email protected]> wrote: > > > I'm afraid that logging is a little sparse at the moment and no MBeans > are > > exposed. Which bundle is this? org.apache.felix.http.jetty or > > org.apache.felix.http.bundle? And is it sling trunk? Will try to run it > in > > my local environment to see what is happening. > > > > On Tue, Oct 6, 2009 at 8:27 AM, Mark Derricutt <[email protected]> wrote: > > > > > This was run time, when starting up the server I see briefly the sling > > > servlet running and telling me theres no repository (yet), then I get > the > > > 404 coming directly from Jetty, so far it looks like the sling servlet > > > (mounted at / ) is getting lost/unregistered somewhere. > > > > > > Is there anyway to ping the internals of the jetty server and see what > > > servlets are being mounted? Maybe via JMX? > > > > > > I'll continue to try and see whats happening in the morning when I get > > back > > > to the office. > > > > > > On Tue, Oct 6, 2009 at 7:17 PM, Sten Roger Sandvik <[email protected]> > wrote: > > > > > > > Did you have problem when deploying or runtime? > > > > > > > > > > > > > >
