Yeah!!!!! I'm not going crazy (this time)! Thank you so much for trying this out. I will use the 1.0.4 version.
Bruce -----Original Message----- From: Achim Nierbeck [mailto:[email protected]] Sent: Thursday, July 28, 2011 6:05 PM To: [email protected] Subject: Re: PAX web and felix Bruce, You just found a bug in the 1.1.0 version of pax web :-) But I can tell you the 1.0.4 is working all right. I also replaced your logging bundles by pax logging this way you get more detail on what happens :-) Regards, Achim Am 28.07.2011 18:46, schrieb Bruce Hartman: > Thank you. I tried 3.1.8 (the full version) and got the same problem. I > might try older versions of PAX Web until one works (0.1.7 worked with the > console). > > If anyone wants to try, load the bundles that I have below into a basic felix > setup (or a subset - you probably don't need them all) and try it. If you do > or don't get the same problem, I would be facinated either way. > > Thanks Achim, > > Bruce > > -----Original Message----- > From: Achim Nierbeck [mailto:[email protected]] > Sent: Thursday, July 28, 2011 10:33 AM > To: [email protected] > Subject: Re: PAX web and felix > > Hi > > could you try the 3.1.8 version, that's the one used inside Karaf, > known to work :-) > > regards, Achim > > 2011/7/28 Bruce Hartman<[email protected]>: >> Here's the error I'm getting trying to run pax Web 1.1.0 with the Felix Web >> console: >> >> -> 89 [FelixStartLevel] INFO org.eclipse.jetty.util.log - >> jetty-7.x.y-SNAPSHOT >> 108 [FelixStartLevel] INFO >> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl - Pax Web available >> at [0.0.0.0]:[8888] >> 118 [FelixStartLevel] INFO org.eclipse.jetty.util.log - Started >> [email protected]:8888 STARTING >> 122 [FelixStartLevel] INFO >> org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl - Binding bundle: >> [org.apache.felix.webconsole [6]] to http service >> ERROR: EventDispatcher: Error during dispatch. >> (java.lang.IllegalStateException: ServletConfig has not been initialized) >> java.lang.IllegalStateException: ServletConfig has not been initialized >> at >> javax.servlet.GenericServlet.getServletContext(GenericServlet.java:185) >> at javax.servlet.GenericServlet.log(GenericServlet.java:306) >> at >> org.apache.felix.webconsole.internal.servlet.OsgiManager.log(OsgiManager.java:561) >> at >> org.apache.felix.webconsole.internal.servlet.OsgiManager.bindHttpService(OsgiManager.java:736) >> at >> org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.addingService(OsgiManager.java:650) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.track(ServiceTracker.java:1008) >> at >> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:933) >> at >> org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:871) >> at >> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:733) >> at >> org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:662) >> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:3721) >> at org.apache.felix.framework.Felix.access$000(Felix.java:80) >> >> Here's the bundles I have installed: >> >> [ 0] [Active ] [ 0] System Bundle (3.0.6) >> [ 1] [Active ] [ 1] Apache Felix Bundle Repository (1.6.2) >> [ 2] [Active ] [ 1] Apache Felix Configuration Admin Service (1.2.8) >> [ 3] [Active ] [ 1] Apache Felix Log Service (1.0.0) >> [ 4] [Active ] [ 1] Apache Felix Shell Service (1.4.2) >> [ 5] [Active ] [ 1] Apache Felix Shell TUI (1.4.1) >> [ 6] [Active ] [ 1] Apache Felix Web Management Console (3.1.6) >> [ 7] [Active ] [ 1] OPS4J Pax Web - Extender - WAR (1.1.0) >> [ 8] [Active ] [ 1] OPS4J Pax Web - Jetty Bundle (1.1.0) >> [ 9] [Active ] [ 1] OPS4J Pax Web - Jsp Support (1.1.0) >> [ 10] [Active ] [ 1] slf4j-api (1.6.1) >> [ 11] [Resolved ] [ 1] slf4j-simple (1.6.1) >> >> >> Any help or advice someone has is appreciated very much. >> >> Thanks, >> >> Bruce >> >> -----Original Message----- >> From: Bruce Hartman [mailto:[email protected]] >> Sent: Thursday, July 28, 2011 9:39 AM >> To: [email protected] >> Subject: RE: PAX web and felix >> >> Thanks. Has anyone else had problems running the Felix Web console with the >> newer versions of PAX web? >> >> Bruce >> >> -----Original Message----- >> From: Achim Nierbeck [mailto:[email protected]] >> Sent: Thursday, July 28, 2011 2:19 AM >> To: [email protected] >> Subject: Re: PAX web and felix >> >> Hi, >> >> well I strongly suggest to use a newer version like 1.0.4 or 1.1.0. >> Now regarding your Issue with the webconsole, interesting since in Apache >> Karaf >> we don't have such issues there. You might take a look at what >> versions and what dependencies >> we used in Karaf or I don't know about your usecase you might take a >> look at Karaf >> since it pretty much does cover all you need to get a HTTP-Service or >> WAB or WAR running >> in OSGi. >> >> Regards, Achim >> >> 2011/7/27 Bruce Hartman<[email protected]>: >>> I'm attempting to get jsp to work in a bundle. >>> >>> I loaded the three pax bundles: >>> OPS4J Pax Web - Jetty Bundle (0.7.3) >>> OPS4J Pax Web - Jsp Support (0.7.3) >>> OPS4J Pax Web - Extender - WAR (0.7.3) >>> >>> (I didn't use the newer versions because I couldn't get the Apache Felix >>> Web Management Console (3.1.6) bundle working with it). >>> >>> I then added the following to a service tracker: >>> >>> httpContext = webContainer.createDefaultHttpContext(); >>> webContainer.registerServlet("/frameworkservlet", new >>> FrameworkServlet(), null, httpContext); >>> webContainer.registerJsps(new String[]{ "*.jsp" }, httpContext); >>> webContainer.registerResources("/", "/war", httpContext); >>> >>> My manifest file has the entry: >>> Web-ContextPath: /war >>> >>> My bundle has a "war" directory, with a jsp directory under that. >>> >>> All html (and other) pages work just fine. For example, if I put a >>> index.html file in my war directory, it is addressable as >>> http://<ip>:<port>/index.html. JSP files are working differently, though. >>> If I put an index.jsp in my war/jsp directory, my jsp file is only >>> addressable by http://<ip>:<port>/war/jsp/index.jsp (I would expect that >>> "/war/" would not be necessary as part of the path. Furthermore, I can't >>> seem to access CSS files and other resources from my jsp file no matter >>> what path I put in. >>> >>> If I changes the registerJsps call to new String[]{"/jsp/*"}, I cannot >>> access the jsp file from the browser at all (no matter what path I use). >>> >>> I don't have a web.xml file. I don't think I need one (based on the fact >>> that html is working just fine). >>> >>> Am I missing something here? Do I have to add something else to my >>> manifest? >>> >>> Thanks in advance for any help/advice. Let me know if you need more >>> clarification >>> >>> Bruce >>> >>> *************************************************************************************** >>> This e-mail and its attachments are private and may contain confidential >>> and proprietary information that is protected. >>> If you are not the intended recipient, you are hereby notified that any >>> disclosure, copying, distribution or use of the >>> information contained in or attached to this message is strictly >>> prohibited. If you have received this e-mail in error, >>> please notify the sender by replying to this message, and then delete it >>> from your system. Thank you. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> -- >> -- >> *Achim Nierbeck* >> >> >> Apache Karaf<http://karaf.apache.org/> Committer& PMC >> OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> >> Committer& Project Lead >> blog<http://notizblog.nierbeck.de/> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> *************************************************************************************** >> This e-mail and its attachments are private and may contain confidential and >> proprietary information that is protected. >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or use of the >> information contained in or attached to this message is strictly prohibited. >> If you have received this e-mail in error, >> please notify the sender by replying to this message, and then delete it >> from your system. Thank you. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> *************************************************************************************** >> This e-mail and its attachments are private and may contain confidential and >> proprietary information that is protected. >> If you are not the intended recipient, you are hereby notified that any >> disclosure, copying, distribution or use of the >> information contained in or attached to this message is strictly prohibited. >> If you have received this e-mail in error, >> please notify the sender by replying to this message, and then delete it >> from your system. Thank you. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > -- -- *Achim Nierbeck* Apache Karaf<http://karaf.apache.org/> Committer& PMC OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer& Project Lead blog<http://notizblog.nierbeck.de/> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] *************************************************************************************** This e-mail and its attachments are private and may contain confidential and proprietary information that is protected. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited. If you have received this e-mail in error, please notify the sender by replying to this message, and then delete it from your system. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
