After looking at it today with a fresh set of eyes, the dependencies all appear to be correct. The problem seems to be that in upgrading to maven 3 and maven eclipse plugin 2.9 the built JSPs aren't in a location where eclipse wants them. When I run it in our production mode (i.e. outside of eclipse) it is running fine.
Cheers, Craig On Fri, Apr 20, 2012 at 3:09 PM, Craig Ching <[email protected]> wrote: > Hi Jan and Jesse, > > Sorry to take so long getting back to you on this, but I'm still having > problems and I just upgraded to jetty 7.6.3.v20120416. Basically, I > started over from scratch with our jetty dependencies, starting with > getting a "mvn dependency:tree" for just o.e.j.osgi.boot and > o.e.j.osgi.boot.jsp. Here is a short status output from everything we have > installed from doing that: > > ss jetty > > Framework is launched. > > id State Bundle > 161 ACTIVE org.eclipse.jetty.continuation_7.6.3.v20120416 > 162 ACTIVE org.eclipse.jetty.deploy_7.6.3.v20120416 > 163 ACTIVE org.eclipse.jetty.http_7.6.3.v20120416 > 164 ACTIVE org.eclipse.jetty.io_7.6.3.v20120416 > 165 ACTIVE org.eclipse.jetty.jmx_7.6.3.v20120416 > 166 ACTIVE org.eclipse.jetty.nested_7.6.3.v20120416 > 167 ACTIVE org.eclipse.jetty.osgi.boot_7.6.3.v20120416 > Fragments=168 > 168 RESOLVED org.eclipse.jetty.osgi.boot.jsp_7.6.3.qualifier > Master=167 > 169 ACTIVE org.eclipse.jetty.security_7.6.3.v20120416 > 170 ACTIVE org.eclipse.jetty.server_7.6.3.v20120416 > 171 ACTIVE org.eclipse.jetty.servlet_7.6.3.v20120416 > 172 ACTIVE org.eclipse.jetty.util_7.6.3.v20120416 > 173 ACTIVE org.eclipse.jetty.webapp_7.6.3.v20120416 > 174 ACTIVE org.eclipse.jetty.xml_7.6.3.v20120416 > 179 ACTIVE org.mortbay.jetty.util_6.1.25 > > osgi> ss servlet > > Framework is launched. > > id State Bundle > 103 ACTIVE javax.servlet_2.5.0.v201103041518 > 104 ACTIVE javax.servlet.jsp_2.1.0.v201105211820 > 105 ACTIVE javax.servlet.jsp.jstl_1.2.0.v201105211821 > 169 ACTIVE org.eclipse.jetty.servlet_7.6.3.v20120416 > > osgi> ss glassfish > > Framework is launched. > > id State Bundle > 111 ACTIVE org.apache.jasper.glassfish_2.1.0.v201110031002 > 112 ACTIVE > org.apache.taglibs.standard.glassfish_1.2.0.v201112081803 > > osgi> ss el > > Framework is launched. > > id State Bundle > 92 ACTIVE com.sun.el_1.0.0.v201105211818 > 102 ACTIVE javax.el_2.1.0.v201105211819 > > osgi> ss jdt > > Framework is launched. > > id State Bundle > 160 ACTIVE org.eclipse.jdt.core.compiler.batch_3.7.0.M20110909-1335 > > > (NOTE that we do have jetty.util 6.1.25 for another third party lib that > requires that particular version, go figure). > > And when I try to access the jsp (we precompile if that matters here), I > get: > > HTTP ERROR 404 > > Problem accessing /bmmadmin/ui/login.jsp. Reason: > > Servlet Not Initialized > > Caused by: > > javax.servlet.UnavailableException: Servlet Not Initialized > at > org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:536) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1361) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:366) > at > org.springframework.security.web.access.channel.ChannelProcessingFilter.doFilter(ChannelProcessingFilter.java:109) > at > org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:378) > at > org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:167) > at > org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:237) > at > org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167) > at > org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1332) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:477) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1031) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:965) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) > at org.eclipse.jetty.server.Server.handle(Server.java:348) > at > org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:452) > at > org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:47) > at > org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:884) > at > org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:938) > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:630) > at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:230) > at > org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:66) > at > org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:254) > at > org.eclipse.jetty.server.ssl.SslSocketConnector$SslConnectorEndPoint.run(SslSocketConnector.java:665) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538) > at java.lang.Thread.run(Thread.java:662) > > > > Am I still missing something? This is pretty typical of what we do and > what we run into. At this point we start combing the jetty distribution > directly and adding any jars (bundles) that we're missing from the > distribution. Any help is much appreciated! > > Cheers, > Craig > > > On Thu, Mar 22, 2012 at 1:16 AM, Jan Bartel <[email protected]> wrote: > >> Craig, >> >> the jetty-jsp-2.1 module is not required (can't remember precisely >> when, but it was a release or so ago). >> >> Whilst the module jetty-jsp exists, it is now just a maven convenience >> for gathering all jsp related dependencies in the one pom. If you're >> using osgi, then you should probably be using the jetty-osgi bundles >> jetty-osgi-boot and jetty-osgi-boot-jsp - these are not in the >> jetty-distribution but are available for download from maven central - >> which have imports for the right jsp dependencies. >> >> Jan >> >> On 22 March 2012 13:19, Craig Ching <[email protected]> wrote: >> > Hi Jesse, >> > >> > I reported some issues with JSP awhile back (I believe against 7.5.4) >> and >> > you had mentioned using the Orbit dependencies. I had tried that and it >> > didn't help, but I didn't have the time to look into it further. >> What's the >> > best way to test the latest and report problems? Get the source and >> build I >> > assume? I'd like to ensure that we get our problems resolved and I'm >> > willing to help! >> > >> > Cheers, >> > Craig >> > >> > On Fri, Mar 9, 2012 at 1:51 PM, Jesse McConnell < >> [email protected]> >> > wrote: >> >> >> >> We have pushed the 7.6.2.v20120308 and 8.1.2.v20120308 releases and >> >> they are now available for download from maven central and the usual >> >> eclipse and codehaus download locations. >> >> >> >> We anticipate another release that will resolve a few lingering jsp >> >> issues related to OSGI usage so if your an osgi user you might want to >> >> wait for the next release before updating. >> >> >> >> cheers, >> >> jesse >> >> >> >> The following issues were resolved in both releases: >> >> >> >> + 370387 SafariWebsocketDraft0Test failure during build. >> >> + 371168 Update ClientCrossContextSessionTest >> >> + 372093 handle quotes in Require-Bundle manifest string >> >> + 372457 Big response + slow clients + pipelined requests cause Jetty >> >> spinning >> >> and eventually closing connections. Added a TODO for a method >> renaming >> >> that >> >> will happen in the next major release (to avoid break implementers). >> >> + 372487 JDBCSessionManager does not work with Oracle >> >> + 372806 Command line should accept relative paths for xml config >> files >> >> + 373037 jetty.server.Response.setContentLength(int) should not close >> a >> >> Writer >> >> when length=0 >> >> + 373162 add improved implementation for getParameterMap(), needs a >> test >> >> though and the existing setup doesn't seem like it would easily >> support >> >> the >> >> needed test so need to do that still >> >> + 373306 Set default user agent extraction pattern for UserAgentFilter >> >> + 373567 cert validation issue with ocsp and crldp always being >> enabled >> >> when >> >> validating turned on fixed >> >> + JETTY-1409 GzipFilter will double-compress application/x-gzip >> content >> >> + JETTY-1489 WebAppProvider attempts to deploy .svn folder >> >> + JETTY-1494 . >> >> >> >> >> >> -- >> >> jesse mcconnell >> >> [email protected] >> >> _______________________________________________ >> >> jetty-users mailing list >> >> [email protected] >> >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >> > >> > >> > _______________________________________________ >> > jetty-users mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
