Hi,

As I'm still on vacation only a quick hint.
Take a look at the PAX Web integration tests. They do use all of the
samples and show which bundles to use.

Regards, Achim

sent from mobile device

Am 09.08.2016 10:05 vorm. schrieb "iJava" <[email protected]>:

> Ok. I finally made it working: I added two bundles:
> pax-web-extender-war-4.2.7.jar
> pax-web-extender-whiteboard-4.2.7.jar
>
> And the server started listen port. However, when I do
> http://127.0.0.1:8080/wab-jetty-web/
> I get
> HTTP ERROR 403  Problem accessing /wab-jetty-web/. Reason:  Forbidden
>
> Could anyone help me solve it? I doubt that I can solve this problem
> without help.
>
> My full log is:
>
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling SLF4J API support.
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling Jakarta Commons Logging API support.
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling Log4J API support.
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling Avalon Logger API support.
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling JULI Logger API support.
> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
> : Enabling Log4J v2 API support. Ignored FQCN: org.apache.logging.log4j.spi.
> AbstractLogger
> [main] INFO org.ops4j.pax.web.service.internal.Activator - EventAdmin
> support enabled, servlet events will be postet to topics.
> [main] INFO org.ops4j.pax.web.service.internal.Activator - LogService
> support enabled, log events will be created.
> [main] INFO org.ops4j.pax.web.service.internal.Activator - Pax Web started
> 2016-08-09 10:58:10.915:INFO::pool-28-thread-1: Logging initialized
> @1184ms
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.JettyFactoryImpl
> - SPDY not available, creating standard ServerConnector for Http
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl
> - Pax Web available at [0.0.0.0]:[8080]
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.internal.HttpServiceFactoryImpl
> - Binding bundle: [org.ops4j.pax.web.samples.wab-jetty-web [41]] to http
> service
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper
> - will add org.apache.jasper.servlet.JasperInitializer to
> ServletContainerInitializers
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.JettyServerWrapper
> - Skipt org.apache.jasper.servlet.JasperInitializer, because specialized
> handler will be present
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext
> - registering context 
> WebAppHttpContext{org.ops4j.pax.web.samples.wab-jetty-web
> - 41}, with context-name: wab-jetty-web
> [pool-28-thread-1] INFO 
> org.ops4j.pax.web.service.jetty.internal.HttpServiceContext
> - registering JasperInitializer
> org.ops4j.pax.web.pax-web-jsp[org.apache.tomcat.util.digester.Digester] :
> addRuleSet() with no namespace URI
> org.ops4j.pax.web.pax-web-jsp[org.apache.tomcat.util.digester.Digester] :
> addRuleSet() with no namespace URI
> 2016-08-09 10:58:11.372:WARN:oejs.ServletContextHandler:pool-28-thread-1:
> ServletContextHandler.setHandler should not be called directly. Use
> insertHandler or setSessionHandler etc.
> [pool-28-thread-1] ERROR org.ops4j.pax.web.jsp.JspServletWrapper -
> Ignored exception
> java.lang.NullPointerException
>     at org.ops4j.pax.web.jsp.JspServletWrapper$1.call(
> JspServletWrapper.java:101)
>     at org.ops4j.pax.web.jsp.JspServletWrapper$1.call(
> JspServletWrapper.java:97)
>     at org.ops4j.pax.swissbox.core.ContextClassLoaderUtils.
> doWithClassLoader(ContextClassLoaderUtils.java:60)
>     at org.ops4j.pax.web.jsp.JspServletWrapper.init(
> JspServletWrapper.java:96)
>     at org.eclipse.jetty.servlet.ServletHolder.initServlet(
> ServletHolder.java:640)
>     at org.eclipse.jetty.servlet.ServletHolder.initialize(
> ServletHolder.java:419)
>     at org.eclipse.jetty.servlet.ServletHandler.initialize(
> ServletHandler.java:875)
>     at org.eclipse.jetty.servlet.ServletContextHandler.startContext(
> ServletContextHandler.java:349)
>     at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.
> startContext(HttpServiceContext.java:590)
>     at org.eclipse.jetty.server.handler.ContextHandler.
> doStart(ContextHandler.java:772)
>     at org.eclipse.jetty.servlet.ServletContextHandler.doStart(
> ServletContextHandler.java:262)
>     at org.ops4j.pax.web.service.jetty.internal.
> HttpServiceContext.doStart(HttpServiceContext.java:249)
>     at org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
>     at org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(
> JettyServerImpl.java:273)
>     at org.ops4j.pax.web.service.internal.HttpServiceStarted.
> end(HttpServiceStarted.java:1095)
>     at org.ops4j.pax.web.service.internal.HttpServiceProxy.end(
> HttpServiceProxy.java:413)
>     at org.ops4j.pax.web.extender.war.internal.
> RegisterWebAppVisitorWC.end(RegisterWebAppVisitorWC.java:380)
>     at org.ops4j.pax.web.extender.war.internal.model.WebApp.
> accept(WebApp.java:692)
>     at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$
> WebAppDependencyListener.register(WebAppPublisher.java:237)
>     at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$
> WebAppDependencyListener.addingService(WebAppPublisher.java:182)
>     at org.ops4j.pax.web.extender.war.internal.WebAppPublisher$
> WebAppDependencyListener.addingService(WebAppPublisher.java:135)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(
> ServiceTracker.java:941)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(
> ServiceTracker.java:870)
>     at org.osgi.util.tracker.AbstractTracked.trackAdding(
> AbstractTracked.java:256)
>     at org.osgi.util.tracker.AbstractTracked.track(
> AbstractTracked.java:229)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.
> serviceChanged(ServiceTracker.java:901)
>     at org.apache.felix.framework.util.EventDispatcher.
> invokeServiceListenerCallback(EventDispatcher.java:991)
>     at org.apache.felix.framework.util.EventDispatcher.
> fireEventImmediately(EventDispatcher.java:839)
>     at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(
> EventDispatcher.java:546)
>     at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
>     at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
>     at org.apache.felix.framework.BundleContextImpl.registerService(
> BundleContextImpl.java:348)
>     at org.apache.felix.framework.BundleContextImpl.registerService(
> BundleContextImpl.java:355)
>     at org.ops4j.pax.web.extender.war.internal.
> DefaultWebAppDependencyManager$1.serviceChanged(
> DefaultWebAppDependencyManager.java:70)
>     at org.ops4j.pax.web.extender.war.internal.
> DefaultWebAppDependencyManager$1.serviceChanged(
> DefaultWebAppDependencyManager.java:61)
>     at org.ops4j.pax.web.extender.war.internal.tracker.
> ReplaceableService.bind(ReplaceableService.java:71)
>     at org.ops4j.pax.web.extender.war.internal.tracker.
> ReplaceableService$Customizer.addingService(ReplaceableService.java:86)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(
> ServiceTracker.java:941)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(
> ServiceTracker.java:870)
>     at org.osgi.util.tracker.AbstractTracked.trackAdding(
> AbstractTracked.java:256)
>     at org.osgi.util.tracker.AbstractTracked.track(
> AbstractTracked.java:229)
>     at org.osgi.util.tracker.ServiceTracker$Tracked.
> serviceChanged(ServiceTracker.java:901)
>     at org.apache.felix.framework.util.EventDispatcher.
> invokeServiceListenerCallback(EventDispatcher.java:991)
>     at org.apache.felix.framework.util.EventDispatcher.
> fireEventImmediately(EventDispatcher.java:839)
>     at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(
> EventDispatcher.java:546)
>     at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4557)
>     at org.apache.felix.framework.Felix.registerService(Felix.java:3549)
>     at org.apache.felix.framework.BundleContextImpl.registerService(
> BundleContextImpl.java:348)
>     at org.ops4j.pax.web.service.internal.Activator.
> updateController(Activator.java:357)
>     at org.ops4j.pax.web.service.internal.Activator$3.run(
> Activator.java:294)
>     at java.util.concurrent.Executors$RunnableAdapter.
> call(Executors.java:511)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
>     at java.lang.Thread.run(Thread.java:745)
> 2016-08-09 10:58:11.381:INFO:oejsh.ContextHandler:pool-28-thread-1:
> Started HttpServiceContext{httpContext=WebAppHttpContext{
> org.ops4j.pax.web.samples.wab-jetty-web - 41}}
> 2016-08-09 10:58:11.383:INFO:oejs.Server:pool-28-thread-1:
> jetty-9.3.9.v20160517
> 2016-08-09 10:58:11.418:INFO:oejs.AbstractConnector:pool-28-thread-1:
> Started default@24f95b66{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
> 2016-08-09 10:58:11.419:INFO:oejs.Server:pool-28-thread-1: Started @1689ms
>
>
>
> On Tuesday, 9 August 2016 10:49:13 UTC+3, iJava wrote:
>>
>> These are my first steps with pax-web, so if I ask something stupid or do
>> something stupid just show me the right direction.
>>
>> I *installed* and *started* the following bundles:
>>
>> javax.servlet-api-3.1.0.jar
>> jetty-util-9.3.9.v20160517.jar
>> jetty-io-9.3.9.v20160517.jar
>> jetty-http-9.3.9.v20160517.jar
>> jetty-server-9.3.9.v20160517.jar
>> jetty-security-9.3.9.v20160517.jar
>> jetty-servlet-9.3.9.v20160517.jar
>> jetty-xml-9.3.9.v20160517.jar
>> slf4j-api-1.7.21.jar
>> slf4j-simple-1.7.21.jar
>> org.objectweb.asm.all-5.0.4.jar
>> xbean-bundleutils-4.5.jar
>> xbean-finder-4.1.jar
>> commons-logging-1.2.jar
>> pax-logging-api-1.8.5.jar
>> pax-web-api-4.2.7.jar
>> pax-web-jetty-4.2.7.jar
>> pax-web-jsp-4.2.7.jar
>> pax-web-runtime-4.2.7.jar
>> pax-web-spi-4.2.7.jar
>> org.apache.felix.fileinstall-3.5.0.jar
>> pax-web-deployer-4.2.7.jar
>> wab-jetty-web-4.2.7.jar          <- sample
>>
>> And this is the ouput:
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling SLF4J API support.
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling Jakarta Commons Logging API support.
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling Log4J API support.
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling Avalon Logger API support.
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling JULI Logger API support.
>> org.ops4j.pax.logging.pax-logging-api[org.ops4j.pax.logging.internal.Activator]
>> : Enabling Log4J v2 API support. Ignored FQCN:
>> org.apache.logging.log4j.spi.AbstractLogger
>> [main] INFO org.ops4j.pax.web.service.internal.Activator - EventAdmin
>> support enabled, servlet events will be postet to topics.
>> [main] INFO org.ops4j.pax.web.service.internal.Activator - LogService
>> support enabled, log events will be created.
>> [main] INFO org.ops4j.pax.web.service.internal.Activator - Pax Web
>> started
>> 2016-08-09 10:43:04.690:INFO::pool-28-thread-1: Logging initialized
>> @1188ms
>> [pool-28-thread-1] INFO 
>> org.ops4j.pax.web.service.jetty.internal.JettyFactoryImpl
>> - SPDY not available, creating standard ServerConnector for Http
>> [pool-28-thread-1] INFO 
>> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl
>> - Pax Web available at [0.0.0.0]:[8080]
>>
>> However, port 8080 is not listened (I check it via netstat). What steps
>> do I miss? Should I activate something? I would be thankful for any help.
>>
>> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
------------------
OPS4J - http://www.ops4j.org - [email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to