| Re: [jetty-users] Cannot deploy a WAB in OSGi Jetty 9 because of javax.naming.NameNotFoundException; remaining name 'java:comp' |
Ok, I reviewed the list I emailed before and excluded all packages and did everything so that my package list looks as much as the one you sent me. Here's the list:lbSTART LEVEL 1ID|State |Level|Name0|Active | 0|System Bundle (5.0.0)1|Active | 1|Apache Felix Gogo Command (0.14.0)2|Active | 1|Apache Felix Gogo Runtime (0.12.1)3|Active | 1|Apache Felix Gogo Shell (0.10.0)5|Active | 1|OSGi Release 4.2.0 Services (3.2.100.v20100503)6|Active | 1|Apache Aries SPI Fly Dynamic Weaving Bundle (1.0.1)7|Active | 1|Apache Aries Util (1.1.0)8|Active | 1|Apache ServiceMix :: Bundles :: bcel (5.2.0.4)9|Active | 1|Apache ServiceMix :: Bundles :: xalan (2.7.2.2)10|Active | 1|Apache ServiceMix :: Bundles :: serializer (2.7.2.1)11|Active | 1|Apache ServiceMix :: Bundles :: xercesImpl (2.11.0.1)12|Active | 1|Apache ServiceMix :: Bundles :: xmlresolver (1.2.0.5)13|Active | 1|Eclipse Compiler for Java(TM) (3.8.2.v20130121-145325)15|Active | 1|Java Server Pages API Bundle (2.1.0.v201105211820)16|Active | 1|Mortbay EL API and Implementation (8.0.20)17|Active | 1|Mortbay Jasper (8.0.20)18|Active | 1|Jetty :: Apache JSP Implementation (9.2.10.v20150310)19|Active | 1|ASM (5.0.3)20|Active | 1|ASM commons classes (5.0.3)21|Active | 1|ASM Tree class visitor (5.0.3)22|Active | 1|Eclipse Compiler for Java(TM) (3.10.2.v20150120-1634)23|Active | 1|geronimo-jta_1.1_spec (1.1.1)24|Active | 1|javax.annotation API (1.2.0)25|Active | 1|javax.mail bundle from Glassfish (1.4.1.v201005082020)26|Active | 1|Java Server Pages Standard Tag Library API Bundle (1.2.0.v201105211821)27|Active | 1|JavaServer Pages (TM) TagLib Implementation (1.2.4)29|Active | 1|Jetty :: XML utilities (9.2.10.v20150310)30|Active | 1|Jetty :: Servlet Annotations (9.2.10.v20150310)31|Active | 1|Jetty :: Continuation (9.2.10.v20150310)32|Active | 1|Jetty :: Deployers (9.2.10.v20150310)33|Active | 1|Jetty :: Http Utility (9.2.10.v20150310)34|Active | 1|Jetty :: IO Utility (9.2.10.v20150310)35|Active | 1|Jetty :: JMX Management (9.2.10.v20150310)36|Active | 1|Jetty :: JNDI Naming (9.2.10.v20150310)37|Installed | 1|Jetty :: OSGi :: Boot (9.2.10.v20150310)38|Installed | 1|Jetty-OSGi-Jasper Integration (9.2.10.v20150310)39|Active | 1|Jetty Servlet API and Schemas for OSGi (3.1.0.M3)40|Active | 1|Jetty :: Plus (9.2.10.v20150310)41|Active | 1|Jetty :: Security (9.2.10.v20150310)42|Active | 1|Jetty :: Server Core (9.2.10.v20150310)43|Active | 1|Jetty :: Servlet Handling (9.2.10.v20150310)44|Active | 1|Jetty :: Utility Servlets and Filters (9.2.10.v20150310)45|Active | 1|Jetty :: Utilities (9.2.10.v20150310)46|Active | 1|Jetty :: Webapp Application Support (9.2.10.v20150310)g! start 372015-05-21 13:07:45.674:INFO::Gogo shell: Logging initialized @175001ms2015-05-21 13:07:45.698:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: Configuring the default jetty server with [file:/D:/NetbeansProjects/hyperstack/target/web/etc/jetty.xml, file:/D:/NetbeansProjects/hyperstack/target/web/etc/jetty-selector.xml, file:/D:/NetbeansProjects/hyperstack/target/web/etc/jetty-deployer.xml]2015-05-21 13:07:45.698:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: JETTY.HOME=D:\NetbeansProjects\hyperstack\target\web2015-05-21 13:07:45.815:INFO:oejs.Server:Gogo shell: jetty-9.2.10.v201503102015-05-21 13:07:45.828:WARN:oejsh.RequestLogHandler:Gogo shell: !RequestLog2015-05-21 13:07:45.892:INFO:oejs.ServerConnector:Gogo shell: Started ServerConnector@5e4ae757{HTTP/1.1}{0.0.0.0:80}2015-05-21 13:07:45.893:INFO:oejs.Server:Gogo shell: Started @175220ms2015-05-21 13:07:45.893:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: Default jetty server configuredg! Started bundle: org.eclipse.jetty.osgi.bootThe only difference from mine and yours is that you installed Xalan by hand and I used the ServiceMix project to get the OSGified Xalan bundle and dependencies (xalan-serializer, xerces, etc) and the JSTL support I use Glassfish instead of Apache as recommended on the Jetty documentation.As you can see, all packages started now including JSP support, Jetty started correctly and running on port 80, but when I deploy a WAB, I'm pretty much back to square one, I get the JNDI java:comp error from jetty-plus.2015-05-21 12:59:23.740:WARN:oejw.WebAppContext:FelixDispatchQueue: Failed startup of context o.e.j.w.WebAppContext@6ff24b9c{/vegos/static,file:/C:/Users/***/AppData/Local/Temp/jetty-0.0.0.0-80-wab-sample2-1.0.0.war-_vegos_static-any-3111516070742142168.dir/webapp/,null}{file:/D:/NetbeansProjects/hyperstack/target/bundle/wab-sample2-1.0.0.war}javax.naming.NameNotFoundException; remaining name 'java:comp'at org.eclipse.jetty.jndi.local.localContextRoot.lookup(localContextRoot.java:429)at org.eclipse.jetty.jndi.local.localContextRoot.lookup(localContextRoot.java:533)at javax.naming.InitialContext.lookup(InitialContext.java:417)at org.eclipse.jetty.plus.webapp.EnvConfiguration.createEnvContext(EnvConfiguration.java:264)at org.eclipse.jetty.plus.webapp.EnvConfiguration.preConfigure(EnvConfiguration.java:72)at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:468)at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:504)at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:41)at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)at org.eclipse.jetty.osgi.boot.BundleWebAppProvider.bundleAdded(BundleWebAppProvider.java:154)at org.eclipse.jetty.osgi.boot.internal.webapp.BundleWatcher.register(BundleWatcher.java:279)at org.eclipse.jetty.osgi.boot.internal.webapp.BundleWatcher.addingBundle(BundleWatcher.java:189)at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:469)at org.osgi.util.tracker.BundleTracker$Tracked.customizerAdding(BundleTracker.java:415)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.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444)at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:913)at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)at org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:516)at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4520)at org.apache.felix.framework.Felix.startBundle(Felix.java:2166)at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:977)at mx.jimi.hyperstack.app.bundles.BundleEventListener.bundleChanged(BundleEventListener.java:23)at org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:913)at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:834)at org.apache.felix.framework.util.EventDispatcher.run(EventDispatcher.java:1143)at org.apache.felix.framework.util.EventDispatcher.access$000(EventDispatcher.java:55)at org.apache.felix.framework.util.EventDispatcher$1.run(EventDispatcher.java:102)at java.lang.Thread.run(Thread.java:745)Ok now this is just silly... On my WAB, I'm doing import packages for * and for javax.naming, if I don't add it I get the class not found for java.naming.factory.initial, do I need to add something else to my WAB then to make it deploy correctly?2015-05-21 11:00 GMT-05:00 Raúl Guerrero Deschamps <raul@xxxxxxxxxxx>:Hi Jan,Following your advice, the test project, and then just working things out along the way, I finally got all bundles to start, but now when I start the Jetty OSGi boot bundle to start the server, I get a really odd exception, and if I go to my browser and run the http://localhost:8080 the server doesn't respond, meaning the server really didn't start. I feel I'm so close to getting this done.Here's what I did and the exception I get:g! lbSTART LEVEL 1ID|State |Level|Name0|Active | 0|System Bundle (5.0.0)1|Active | 1|Apache Felix Gogo Command (0.14.0)2|Active | 1|Apache Felix Gogo Runtime (0.12.1)3|Active | 1|Apache Felix Gogo Shell (0.10.0)4|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/jsp-api-2.1.jar (0.0.0)5|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/jstl-api-1.2.jar (0.0.0)6|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/org.apache.aries.spifly.core-internal-1.0.1.jar (0.0.0)7|Active | 1|Apache Aries SPI Fly Dynamic Weaving Bundle (1.0.1)8|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/org.apache.aries.spifly.weaver-internal-1.0.1.jar (0.0.0)9|Active | 1|Apache Aries Util (1.1.0)10|Active | 1|Apache ServiceMix :: Bundles :: bcel (5.2.0.4)11|Active | 1|Apache ServiceMix :: Bundles :: xalan (2.7.2.2)12|Active | 1|Apache ServiceMix :: Bundles :: serializer (2.7.2.1)13|Active | 1|Apache ServiceMix :: Bundles :: xercesImpl (2.11.0.1)14|Active | 1|Apache ServiceMix :: Bundles :: xmlresolver (1.2.0.5)15|Active | 1|Eclipse Compiler for Java(TM) (3.8.2.v20130121-145325)16|Active | 1|OSGi Release 4.2.0 Services (3.2.100.v20100503)17|Active | 1|osgi.core (5.0.0.201203141902)18|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/org.osgi.foundation-1.2.0.jar (0.0.0)19|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/serializer-2.7.2.jar (0.0.0)20|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/servlet-api-2.5.jar (0.0.0)21|Active | 1|file:/D:/NetbeansProjects/hyperstack/target/bundle/xml-apis-1.4.01.jar (0.0.0)23|Active | 1|Java Server Pages API Bundle (2.1.0.v201105211820)24|Active | 1|Mortbay EL API and Implementation (8.0.20)25|Active | 1|Mortbay Jasper (8.0.20)26|Active | 1|Jetty :: Apache JSP Implementation (9.2.10.v20150310)27|Active | 1|ASM (5.0.3)28|Active | 1|ASM commons classes (5.0.3)29|Active | 1|ASM all classes with debug info (5.0.3)30|Active | 1|ASM Tree class visitor (5.0.3)31|Active | 1|Eclipse Compiler for Java(TM) (3.10.2.v20150120-1634)32|Active | 1|geronimo-jta_1.1_spec (1.1.1)33|Active | 1|Apache Geronimo Activation Plug-in (1.1.0.v201105071233)34|Active | 1|javax.annotation API (1.2.0)35|Active | 1|javax.mail bundle from Glassfish (1.4.1.v201005082020)36|Active | 1|Java Server Pages Standard Tag Library API Bundle (1.2.0.v201105211821)37|Active | 1|JavaServer Pages (TM) TagLib Implementation (1.2.4)39|Active | 1|Jetty :: XML utilities (9.2.10.v20150310)40|Active | 1|Jetty :: Servlet Annotations (9.2.10.v20150310)41|Active | 1|Jetty :: Deployers (9.2.10.v20150310)42|Active | 1|Jetty :: Http Utility (9.2.10.v20150310)43|Active | 1|Jetty :: IO Utility (9.2.10.v20150310)44|Active | 1|Jetty :: JMX Management (9.2.10.v20150310)45|Active | 1|Jetty :: JNDI Naming (9.2.10.v20150310)46|Resolved | 1|Jetty :: OSGi :: Boot (9.2.10.v20150310)47|Resolved | 1|Jetty-OSGi-Jasper Integration (9.2.10.v20150310)48|Active | 1|Jetty Servlet API and Schemas for OSGi (3.1.0.M3)49|Active | 1|Jetty :: Plus (9.2.10.v20150310)51|Active | 1|Jetty :: Security (9.2.10.v20150310)52|Active | 1|Jetty :: Server Core (9.2.10.v20150310)53|Active | 1|Jetty :: Servlet Handling (9.2.10.v20150310)54|Active | 1|Jetty :: Utilities (9.2.10.v20150310)55|Active | 1|Jetty :: Webapp Application Support (9.2.10.v20150310)g! start 462015-05-21 10:36:20.800:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: Configuring the default jetty server with [file:/D:/NetbeansProjects/***/target/web/etc/jetty.xml, file:/D:/NetbeansProjects/***/target/web/etc/jetty-selector.xml, file:/D:/NetbeansProjects/***/target/web/etc/jetty-deployer.xml]2015-05-21 10:36:20.801:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: JETTY.HOME=D:\NetbeansProjects\***\target\web2015-05-21 10:36:20.823:WARN:oejobis.JettyServerServiceTracker:Gogo shell:java.lang.NullPointerExceptionat java.util.regex.Matcher.getTextLength(Matcher.java:1283)at java.util.regex.Matcher.reset(Matcher.java:309)at java.util.regex.Matcher.<init>(Matcher.java:229)at java.util.regex.Pattern.matcher(Pattern.java:1093)at org.eclipse.jetty.osgi.boot.jasper.ContainerTldBundleDiscoverer.getUrlsForBundlesWithTlds(ContainerTldBundleDiscoverer.java:139)at org.eclipse.jetty.osgi.boot.internal.serverfactory.ServerInstanceWrapper.start(ServerInstanceWrapper.java:290)at org.eclipse.jetty.osgi.boot.internal.serverfactory.JettyServerServiceTracker.serviceChanged(JettyServerServiceTracker.java:116)at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:987)at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4536)at org.apache.felix.framework.Felix.registerService(Felix.java:3518)at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:348)at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:322)at org.eclipse.jetty.osgi.boot.internal.serverfactory.DefaultJettyAtJettyHomeHelper.startJettyAtJettyHome(DefaultJettyAtJettyHomeHelper.java:179)at org.eclipse.jetty.osgi.boot.JettyBootstrapActivator.start(JettyBootstrapActivator.java:93)at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697)at org.apache.felix.framework.Felix.activateBundle(Felix.java:2220)at org.apache.felix.framework.Felix.startBundle(Felix.java:2138)at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:977)at org.apache.felix.gogo.command.Basic.start(Basic.java:729)at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:483)at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)at org.apache.felix.gogo.shell.Console.run(Console.java:62)at org.apache.felix.gogo.shell.Shell.console(Shell.java:203)at org.apache.felix.gogo.shell.Shell.gosh(Shell.java:128)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:483)at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:137)at org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:82)at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)at org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)at org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)at org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:92)at org.apache.felix.gogo.shell.Activator.run(Activator.java:75)at java.lang.Thread.run(Thread.java:745)2015-05-21 10:36:20.824:INFO:oejobis.DefaultJettyAtJettyHomeHelper:Gogo shell: Default jetty server configuredg! Started bundle: org.eclipse.jetty.osgi.bootWhat do you think it could be? What am I doing wrong this time that Jetty is not starting?Raul2015-05-21 1:09 GMT-05:00 Jan Bartel <janb@xxxxxxxxxxx>:Raul,
I deployed the jetty-jndi bundle. If you look back at the list I sent
you, you will see:
>14|Active | 1|Jetty :: JNDI Naming (9.2.10.v20150310)
Jan
On 21 May 2015 at 14:27, Raúl Guerrero Deschamps <raul@xxxxxxxxxxx> wrote:
> Hi Jan,
>
> I've already followed the documentation in the first place but really didn't
> work, but I'm going to continue my tests according to the package list you
> sent me, that way I know that it has to work, and JSP has to work now.
>
> Also from what you mention, I'm going to keep trying with 9.2.10 then to
> avoid any more noise from configurations.
>
> I have a question though, how did you manage to avoid JNDI? because I see
> that jetty-plus and jetty-annotations need it according to maven and on the
> list you sent me there is Plus active but no JNDI bundle, and also, by
> removing JNDI, do I remove the 2 system variable Call tags from jetty.xml
> (java.naming.factory.initial and java.naming.factory.url.pkgs)?
>
> Thanks, I know this issue is a bother and taking longer than usual, and as
> soon as I make it work, I'm going to distribute this whole project in GitHub
> so anyone trying to do the same as me can benefit from your help and my
> work.
>
>
> 2015-05-20 19:07 GMT-05:00 Jan Bartel <janb@xxxxxxxxxxx>:
>
>> Raul,
>>
>> If you look at the documentation page here:
>>
>> https://www.eclipse.org/jetty/documentation/current/framework-jetty-osgi.html#d0e20076
>>
>> The only place I've been able to find a xalan and xmlserializer jar
>> with a decent manifest is in Eclipse Orbit. One option for you is to
>> download them manually and use system <scope> with <systemPath>
>> definitions in your pom.
>>
>> BTW if you switch to jetty-9.3, then your set of jetty etc files is
>> different.
>>
>> For 9.2.x it should
>>
>> be:jetty.etc.config.urls=etc/jetty.xml,etc/jetty-testrealm.xml,etc/jetty-selector.xml,etc/jetty-deployer.xml
>>
>> For 9.3 it should
>>
>> be:jetty.etc.config.urls=etc/jetty.xml,etc/jetty-http.xml,etc/jetty-ssl.xml,etc/jetty-https.xml,etc/jetty-testrealm.xml,etc/jetty-deployer.xml
>>
>> Each set of those are available in the appropriate jetty repo (either
>> branch 9.2.x or master) in the
>> jetty-osgi/test-jetty-osgi/src/test/config/etc directory.
>>
>> If I were you, I'd rm -fr felix-cache/* to ensure you've wiped out any
>> past bundle caching.
>>
>> Jan
>>
>> On 20 May 2015 at 23:55, Raúl Guerrero Deschamps <raul@xxxxxxxxxxx> wrote:
>> > Hi Jan,
>> >
>> > The thing is that, even though I followed the test project and your
>> > recommendations, I just don't get the same packages as you!
>> >
>> > I still get errors when trying to start some bundles, I see you get the
>> > Xalan package, but I haven't found it anywhere in maven.
>> >
>> > I moved my Jetty version up to 9.3.0.RC0 just in case there's something
>> > new
>> > on dependencies or anything.
>> >
>> > here's what I get now when starting the bundles that I didn't get
>> > before, I
>> > didn't have any issues with osgi.serviceloader before but now it appears
>> > as
>> > a missing requirement:
>> >
>> >
>> > 8|Installed | 1|Jetty :: Apache JSP Implementation (9.3.0.RC0)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.eclipse.jetty.apache-jsp [8](R 8.0): missing requirement
>> > [org.eclipse.jetty.apache-jsp [8](R 8.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.registrar) Unresolved requirements:
>> > [[org.eclipse.jetty.apache-jsp [8](R 8.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.registrar)]
>> >
>> > 22|Installed | 1|Jetty :: Websocket :: Servlet Interface (9.3.0.RC0)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.eclipse.jetty.websocket.servlet [22](R 22.0): missing requirement
>> > [org.eclipse.jetty.websocket.servlet [22](R 22.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.processor) Unresolved requirements:
>> > [[org.eclipse.jetty.websocket.servlet [22](R 22.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.processor)]
>> >
>> > 26|Installed | 1|Jetty :: Websocket :: Server (9.3.0.RC0)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.eclipse.jetty.websocket.server [26](R 26.0): missing requirement
>> > [org.eclipse.jetty.websocket.server [26](R 26.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.registrar) Unresolved requirements:
>> > [[org.eclipse.jetty.websocket.server [26](R 26.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.registrar)]
>> >
>> > 28|Installed | 1|Jetty :: Websocket :: javax.websocket.server ::
>> > Server
>> > Implementation (9.3.0.RC0)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.eclipse.jetty.websocket.javax.websocket.server [28](R 28.0): missing
>> > requirement [org.eclipse.jetty.websocket.javax.websocket.server [28](R
>> > 28.0)] osgi.wiring.package;
>> >
>> > (&(osgi.wiring.package=org.eclipse.jetty.websocket.server)(version>=9.0.0)(!(version>=10.0.0)))
>> > [caused by: Unable to resolve org.eclipse.jetty.websocket.server [26](R
>> > 26.0): missing requirement [org.eclipse.jetty.websocket.server [26](R
>> > 26.0)]
>> > osgi.extender; (osgi.extender=osgi.serviceloader.registrar)] Unresolved
>> > requirements: [[org.eclipse.jetty.websocket.javax.websocket.server
>> > [28](R
>> > 28.0)] osgi.wiring.package;
>> >
>> > (&(osgi.wiring.package=org.eclipse.jetty.websocket.server)(version>=9.0.0)(!(version>=10.0.0)))]
>> >
>> > 44|Installed | 1|JavaServer Pages (TM) TagLib Implementation (1.2.2)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.glassfish.web.javax.servlet.jsp.jstl [44](R 44.0): missing
>> > requirement
>> > [org.glassfish.web.javax.servlet.jsp.jstl [44](R 44.0)]
>> > osgi.wiring.package;
>> > (osgi.wiring.package=com.sun.org.apache.xalan.internal.res) Unresolved
>> > requirements: [[org.glassfish.web.javax.servlet.jsp.jstl [44](R 44.0)]
>> > osgi.wiring.package;
>> > (osgi.wiring.package=com.sun.org.apache.xalan.internal.res)]
>> >
>> > 63|Installed | 1|Jetty :: Servlet Annotations (9.3.0.RC0)
>> > org.osgi.framework.BundleException: Unable to resolve
>> > org.eclipse.jetty.annotations [63](R 63.0): missing requirement
>> > [org.eclipse.jetty.annotations [63](R 63.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.processor) Unresolved requirements:
>> > [[org.eclipse.jetty.annotations [63](R 63.0)] osgi.extender;
>> > (osgi.extender=osgi.serviceloader.processor)]
>> >
>> >
>> > The way that I'm fetching the bundles is that I created a project POM
>> > that
>> > contains all the bundles as dependencies, and then using the
>> > copy-dependencies maven plugin, it copies all declared dependencies to
>> > the
>> > bundles folder in my Felix installation.
>> >
>> > So, If you use Maven as well, what are the dependencies I need to
>> > declare so
>> > I get the same packages as you? Like I mentioned before, I have a plain
>> > vanilla Felix, so it only comes with the gogo bundles.
>> >
>> > Also, the test project you told me to check out has a lot of
>> > dependencies
>> > declared as test and runtime scopes, so, which ones are actually needed
>> > to
>> > run on execution? which ones of the test scope are used for execution as
>> > well?
>> >
>> > Do you have a POM you can share with me that has all the dependencies
>> > that I
>> > can add to my POM that I told you about that copies everything into the
>> > bundles folder in Felix and actually starts correctly?
>> >
>> >
>> > Thanks so much for the help
>> >
>> > Raul
>> >
>> >
>> > 2015-05-20 0:22 GMT-05:00 Jan Bartel <janb@xxxxxxxxxxx>:
>> >
>> >> Raul,
>> >>
>> >> I've tested our standard jetty test webapp (that does *not* use jndi)
>> >> with felix 5.0.0 and it runs no problems.
>> >>
>> >> Here's the gogo shell output:
>> >>
>> >>
>> >> g! lb
>> >> ID|State |Level|Name
>> >> 0|Active | 0|System Bundle (5.0.0)
>> >> 1|Active | 1|ASM (5.0.1)
>> >> 2|Active | 1|ASM commons classes (5.0.1)
>> >> 3|Active | 1|ASM Tree class visitor (5.0.1)
>> >> 4|Active | 1|geronimo-jta_1.1_spec (1.1.1)
>> >> 5|Active | 1|Jetty :: Websocket :: javax.websocket ::
>> >> Client Implementation (9.2.10.v20150310)
>> >> 6|Active | 1|Jetty :: Websocket :: javax.websocket.server
>> >> :: Server Implementation (9.2.10.v20150310)
>> >> 7|Active | 1|javax.annotation API (1.2.0)
>> >> 8|Active | 1|javax.mail bundle from Glassfish
>> >> (1.4.1.v201005082020)
>> >> 9|Active | 1|WebSocket server API (1.0.0)
>> >> 10|Active | 1|Jetty :: Servlet Annotations (9.2.10.v20150310)
>> >> 11|Active | 1|Jetty :: Deployers (9.2.10.v20150310)
>> >> 12|Active | 1|Jetty :: Http Utility (9.2.10.v20150310)
>> >> 13|Active | 1|Jetty :: IO Utility (9.2.10.v20150310)
>> >> 14|Active | 1|Jetty :: JNDI Naming (9.2.10.v20150310)
>> >> 15|Active | 1|Jetty :: OSGi :: Boot (9.2.10.v20150310)
>> >> 16|Resolved | 1|Jetty-OSGi-Jasper Integration
>> >> (9.2.10.v20150310)
>> >> 17|Active | 1|Jetty Servlet API and Schemas for OSGi
>> >> (3.1.0.M3)
>> >> 18|Active | 1|Jetty :: Plus (9.2.10.v20150310)
>> >> 19|Active | 1|Jetty :: Rewrite Handler (9.2.10.v20150310)
>> >> 20|Active | 1|Jetty :: Security (9.2.10.v20150310)
>> >> 21|Active | 1|Jetty :: Server Core (9.2.10.v20150310)
>> >> 22|Active | 1|Jetty :: Servlet Handling (9.2.10.v20150310)
>> >> 23|Active | 1|Jetty :: Utility Servlets and Filters
>> >> (9.2.10.v20150310)
>> >> 24|Active | 1|Jetty :: Utilities (9.2.10.v20150310)
>> >> 25|Active | 1|Jetty :: Webapp Application Support
>> >> (9.2.10.v20150310)
>> >> 26|Active | 1|Jetty :: XML utilities (9.2.10.v20150310)
>> >> 27|Active | 1|Apache Aries SPI Fly Dynamic Weaving Bundle
>> >> (1.0.1)
>> >> 28|Active | 1|Apache Aries Util (1.0.0)
>> >> 29|Active | 1|Apache Felix Bundle Repository (2.0.4)
>> >> 30|Active | 1|Apache Felix Configuration Admin Service
>> >> (1.8.4)
>> >> 31|Active | 1|Apache Felix EventAdmin (1.4.2)
>> >> 32|Active | 1|Apache Felix Gogo Command (0.14.0)
>> >> 33|Active | 1|Apache Felix Gogo Runtime (0.16.2)
>> >> 34|Active | 1|Apache Felix Gogo Shell (0.10.0)
>> >> 35|Active | 1|Apache Felix Log Service (1.0.1)
>> >> 36|Active | 1|Apache Standard Taglib Implementation (1.2.1)
>> >> 37|Active | 1|Apache Standard Taglib Specification API
>> >> (1.2.1)
>> >> 38|Active | 1|Xalan-Java (2.7.1.v201005080400)
>> >> 39|Active | 1|Apache XML Commons Serializer
>> >> (2.7.1.v201005080400)
>> >> 40|Active | 1|Jetty :: Apache JSP Implementation
>> >> (9.2.10.v20150310)
>> >> 41|Active | 1|Eclipse Compiler for Java(TM)
>> >> (3.8.2.v20130121-145325)
>> >> 42|Active | 1|Mortbay EL API and Implementation (8.0.9)
>> >> 43|Active | 1|Mortbay Jasper (8.0.9)
>> >> 44|Active | 1|Jetty :: Websocket :: API (9.2.10.v20150310)
>> >> 45|Active | 1|Jetty :: Websocket :: Client (9.2.10.v20150310)
>> >> 46|Active | 1|Jetty :: Websocket :: Common (9.2.10.v20150310)
>> >> 47|Active | 1|Jetty :: Websocket :: Server (9.2.10.v20150310)
>> >> 48|Active | 1|Jetty :: Websocket :: Servlet Interface
>> >> (9.2.10.v20150310)
>> >>
>> >> g! install
>> >>
>> >> file:/usr/local/java/felix/felix-framework-5.0.0/jetty-webapp-bundles-9.2.10/test-jetty-webapp-9.2.11-SNAPSHOT-webbundle.jar
>> >> Bundle ID: 49
>> >> g! start 49
>> >> 2015-05-20 15:13:59.844:DBUG:oejpw.EnvConfiguration:Gogo shell:
>> >> Created java:comp/env for webapp /
>> >> 2015-05-20 15:13:59.845:DBUG:oejpw.EnvConfiguration:Gogo shell:
>> >> Binding env entries from the jvm scope
>> >> 2015-05-20 15:13:59.847:DBUG:oejpw.EnvConfiguration:Gogo shell:
>> >> Binding env entries from the server scope
>> >> 2015-05-20 15:13:59.848:DBUG:oejpw.EnvConfiguration:Gogo shell:
>> >> Binding env entries from the context scope
>> >> 2015-05-20 15:14:00.885:INFO:oejsh.ContextHandler:Gogo shell: Started
>> >>
>> >>
>> >> o.e.j.w.WebAppContext@4e5d3431{/,file:/tmp/jetty-0.0.0.0-8080-test-jetty-webapp-9.2.11-SNAPSHOT-webbundle.jar-_-any-7268102787456536697.dir/webapp/,AVAILABLE}{/test.war}
>> >>
>> >> My conf/system.properties contains:
>> >>
>> >> [2887] cat conf/system.properties
>> >> jetty.port=8080
>> >> jetty.home=/usr/local/java/felix/felix-framework-5.0.0/jetty-home
>> >>
>> >>
>> >> jetty.etc.config.urls=etc/jetty.xml,etc/jetty-testrealm.xml,etc/jetty-selector.xml,etc/jetty-deployer.xml
>> >> #org.eclipse.jetty.annotations.LEVEL=DEBUG
>> >> #org.eclipse.jetty.osgi.LEVEL=DEBUG
>> >> #org.eclipse.jetty.webapp.LEVEL=DEBUG
>> >> org.eclipse.jetty.plus.webapp.EnvConfiguration.LEVEL=DEBUG
>> >>
>> >> My conf/config.properties sets the org.osgi.framework.system.packages
>> >> property to a rather long list of packages. If you need it, the value
>> >> of property is pasted here: http://pastebin.com/T0j9kEpt
>> >>
>> >>
>> >> I used the xml files from the
>> >> jetty-osgi/test-jetty-osgi/src/test/config/etc dir in the jetty repo
>> >> and copied them into
>> >> /usr/local/java/felix/felix-framework-5.0.0/jetty-home/etc.
>> >>
>> >> I used the standard test-jetty-webapp as a webbundle. It isn't
>> >> uploaded to maven, so the only way to get it is to checkout jetty and
>> >> build it (use the jetty-9.2.x branch). You'll find it in
>> >> tests/test-webapps/test-jetty-webapp/target with a -webbundle suffix.
>> >>
>> >> Notice that the jetty-annotations jar requires a jta api jar. The
>> >> geronimo one is the only one that has a correct osgi manifest that
>> >> does not bring in a lot of extraneous and unneeded dependencies. You
>> >> don't have that listed on your output, so I don't know how the
>> >> jetty-annotations jar is being resolved for you.
>> >>
>> >> You also have the javax.servlet: javax.servlet-api 3.1.0 jar listed on
>> >> your deployed bundles - do not use that as it does not have a good
>> >> osgi manifest. You already have the org.eclipse.jetty.toolchain:
>> >> jetty-osgi-servlet-api 3.1.0.M3 deployed, which is all you should
>> >> need, so undeploy the javax.servlet-api one.
>> >>
>> >> The test-jetty-webapp requires the jetty-rewrite, jetty-sevlets, and
>> >> all the websocket jars, which is why you see them listed above.
>> >>
>> >> regards
>> >> Jan
>> >>
>> >> On 20 May 2015 at 08:23, Jan Bartel <janb@xxxxxxxxxxx> wrote:
>> >> > Raul,
>> >> >
>> >> >
>> >> >> My OSGi container is a plain Felix 5.0.0 downloaded from
>> >> >> felix.apache.org
>> >> >> and it only has the gogo bundles to get the command line.
>> >> >>
>> >> >> The bundles I have deployed I chose them because the OSGi page on
>> >> >> the
>> >> >> Jetty
>> >> >> documentation mentions them as needed
>> >> >>
>> >> >>
>> >> >> http://eclipse.org/jetty/documentation/current/framework-jetty-osgi.html I
>> >> >> only selected the servlet and annotation support ones, as I haven't
>> >> >> been
>> >> >> able to make the JSP support bundles work correctly with either the
>> >> >> Glassfish or the Apache bundles, on deploy they kill my Felix
>> >> >> instance,
>> >> >> so
>> >> >> the documentation is wrong there as well.
>> >> >
>> >> > The jetty osgi bundles with the glassfish or apache bundles have been
>> >> > tested and verified as working with felix 4.4.1. I'll download
>> >> > felix-5
>> >> > and double-check against that as well.
>> >> >
>> >> >>
>> >> >> The packages from org.eclipse.jetty are all version 9.2.10.v20150310
>> >> >>
>> >> >> The packages I have deployed are:
>> >> >> org.eclipse.jetty.osgi: jetty-osgi-boot
>> >> >> org.eclipse.jetty: jetty-util
>> >> >> org.eclipse.jetty: jetty-http
>> >> >> org.eclipse.jetty: jetty-io
>> >> >> org.eclipse.jetty: jetty-security
>> >> >> org.eclipse.jetty: jetty-server
>> >> >> org.eclipse.jetty: jetty-servlet
>> >> >> org.eclipse.jetty: jetty-webapp
>> >> >> org.eclipse.jetty: jetty-deploy
>> >> >> org.eclipse.jetty: jetty-xml
>> >> >> org.eclipse.jetty.toolchain: jetty-osgi-servlet-api 3.1.0.M3
>> >> >> javax.servlet: javax.servlet-api 3.1.0
>> >> >> org.eclipse.jetty: jetty-jndi
>> >> >> org.eclipse.jetty: jetty-plus
>> >> >> org.eclipse.jetty: jetty-annotations
>> >> >> org.eclipse.jetty.orbit: javax.mail.glassfish 1.4.1.v201005082020
>> >> >> org.ow2.asm: asm 5.0.3
>> >> >> org.ow2.asm: asm-commons 5.0.3
>> >> >> org.ow2.asm: asm-tree 5.0.3
>> >> >> org.apache.aries: org.apache.aries.util 1.1.0
>> >> >> org.apache.aries.spifly: org.apache.aries.spifly.dynamic.bundle
>> >> >> 1.0.1
>> >> >> javax.annotation: javax.annotation-api 1.2
>> >> >>
>> >> >> And I'm also going to need Jersey support so I have also deployed
>> >> >> these
>> >> >> (all
>> >> >> version 2.17):
>> >> >> org.glassfish.jersey.core: jersey-server
>> >> >> org.glassfish.jersey.core: jersey-common
>> >> >> org.glassfish.jersey.containers: jersey-container-jetty-servlet
>> >> >> org.glassfish.jersey.media: jersey-media-json-jackson
>> >> >>
>> >> >> But I have tried it without having the Jersey bundles deployed and
>> >> >> get
>> >> >> the
>> >> >> error, so I think it's not that.
>> >> >>
>> >> >> As you can see, it's all the packages mentioned in the OSGi
>> >> >> documentation,
>> >> >> and the 3 configurations files in the etc folder (jetty.xml,
>> >> >> jetty-selector.xml and jetty-deployer.xml) I took them from
>> >> >>
>> >> >>
>> >> >> https://eclipse.googlesource.com/jetty/org.eclipse.jetty.project/+/jetty-9.2.x/jetty-osgi/jetty-osgi-boot/jettyhome/etc/
>> >> >> because the files are nowhere to be found on the documentation, I
>> >> >> actually
>> >> >> added an issue on the github.com for Jetty documentation on this. I
>> >> >> use
>> >> >> the
>> >> >> default files, I didn't do any modifications to them.
>> >> >
>> >> > Those files are present inside the jetty-osgi-boot.jar. It might be
>> >> > nice if jetty used those if neither of the system properties were
>> >> > found. I'll make a bug for that.
>> >> >
>> >> >>
>> >> >> And you know what, I don't use JNDI whatsoever, so if I could
>> >> >> disable
>> >> >> it
>> >> >> altogether it would be awesome, but apparently the jetty-plus and
>> >> >> jetty-annotation bundles depend on it, and I do need the servlet
>> >> >> annotation
>> >> >> support.
>> >> >>
>> >> >> How do I enable JNDI logging?
>> >> >
>> >> > Set the normal jetty logging property in the
>> >> > felix/conf/system.properties file. Ie
>> >> > org.eclipse.jetty.jndi.LEVEL=DEBUG. Also throw in
>> >> > org.eclipse.jetty.webapp.LEVEL=DEBUG.
>> >> >
>> >> >
>> >> > Also have a look in the jetty github repo in the
>> >> > jetty-osgi/test-jetty-osgi directory. There are a number of unit
>> >> > tests
>> >> > where we deploy the standard jetty test webapps, all with jsp, some
>> >> > with jndi and annotations and some without - look at the way they're
>> >> > deployed and compare to your setup to see if you can work out what is
>> >> > different.
>> >> >
>> >> > regards
>> >> > Jan
>> >> >
>> >> >
>> >> >>
>> >> >> Thanks.
>> >> >>
>> >> >> Raul
>> >> >>
>> >> >>
>> >> >>>
>> >> >>>
>> >> >>> Date: Tue, 19 May 2015 08:45:33 +1000
>> >> >>> From: Jan Bartel <janb@xxxxxxxxxxx>
>> >> >>> To: JETTY user mailing list <jetty-users@xxxxxxxxxxx>
>> >> >>> Subject: Re: [jetty-users] Cannot deploy a WAB in OSGi Jetty 9
>> >> >>> because
>> >> >>> of javax.naming.NameNotFoundException; remaining name
>> >> >>> 'java:comp'
>> >> >>> Message-ID:
>> >> >>>
>> >> >>>
>> >> >>> <CALg=Vpgs_5Dq6d0-p7g1m7qgp7TGATdYr1+2XY5mY4kXZJ4b0A@xxxxxxxxxxxxxx>
>> >> >>> Content-Type: text/plain; charset=UTF-8
>> >> >>>
>> >> >>>
>> >> >>> Raul,
>> >> >>>
>> >> >>> Can you post what osgi environment you are deploying into, and what
>> >> >>> version. Please also post the list of bundles that you have
>> >> >>> deployed.
>> >> >>>
>> >> >>> The jndi exception is odd. The jndi mechanism is only used if
>> >> >>> appropriate jndi classes are detected on the classpath. So it looks
>> >> >>> like those classes are detected. However, I can see that the setup
>> >> >>> is
>> >> >>> not correct, because the lookup for "java:comp" is being done in
>> >> >>> the
>> >> >>> default server namespace instead of the special "java:" namespace
>> >> >>> provided by jetty.
>> >> >>>
>> >> >>> To setup the "java:" namespace correctly, jetty needs some system
>> >> >>> properties defined. These are in the jetty.xml file here:
>> >> >>>
>> >> >>> <Call class="java.lang.System" name="setProperty">
>> >> >>> <Arg>java.naming.factory.initial</Arg>
>> >> >>> <Arg><Property name="java.naming.factory.initial"
>> >> >>> default="org.eclipse.jetty.jndi.InitialContextFactory"/></Arg>
>> >> >>> </Call>
>> >> >>> <Call class="java.lang.System" name="setProperty">
>> >> >>> <Arg>java.naming.factory.url.pkgs</Arg>
>> >> >>> <Arg><Property name="java.naming.factory.url.pkgs"
>> >> >>> default="org.eclipse.jetty.jndi"/></Arg>
>> >> >>> </Call>
>> >> >>>
>> >> >>> The second of those properties is required for "java:" namespace.
>> >> >>>
>> >> >>> Can you dump your osgi setup environment to double check that those
>> >> >>> values are set?
>> >> >>>
>> >> >>> Please also post the output you get if you run with logging enabled
>> >> >>> for org.eclipse.jetty.jndi package.
>> >> >>>
>> >> >>> Jan
>> >> >>>
>> >> >>>
>> >> >>> On 19 May 2015 at 03:23, Ra?l Guerrero Deschamps <raul@xxxxxxxxxxx>
>> >> >>> wrote:
>> >> >>> > I'm trying to deploy a simple WAB application inside an OSGi
>> >> >>> > container
>> >> >>> > that
>> >> >>> > has installed the Jetty 9.2.10 bundles and the JAX-RS Jersey 2.17
>> >> >>> > bundles.
>> >> >>> >
>> >> >>> > All the bundles start correctly and without issues, and when I
>> >> >>> > install
>> >> >>> > my
>> >> >>> > WAB it also installs correctly, but when I start my WAB it sends
>> >> >>> > a
>> >> >>> > JNDI
>> >> >>> > name
>> >> >>> > not found exception, it's really odd because I don't use JNDI
>> >> >>> > whatsoever
>> >> >>> > in
>> >> >>> > my WAB, and the name that the exception is referencing is
>> >> >>> > completely
>> >> >>> > bogus,
>> >> >>> > because it just states the missing JNDI resource name is
>> >> >>> > 'java:comp',
>> >> >>> > which
>> >> >>> > is just the Jetty prefix for JNDI resources, so some Jetty bundle
>> >> >>> > must
>> >> >>> > be
>> >> >>> > trying to setup an empty JNDI resource which causes the problem.
>> >> >>> >
>> >> >>> > 2015-05-15
>> >> >>> > 23:48:29.968:WARN:oejw.WebAppContext:FelixDispatchQueue:
>> >> >>> > Failed
>> >> >>> > startup of context
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > o.e.j.w.WebAppContext@5718e0e{/wab,file:/private/var/folders/3h/w04868ln4j30dwqdscvy8wnw0000gn/T/jetty-0.0.0.0-8080-wab-sample-1.0.0.war-_wab-any-3819588013061278932.dir/webapp/,null}{file:/Users/****/NetbeansProjects/*****/target/bundle/wab-sample-1.0.0.war}
>> >> >>> > javax.naming.NameNotFoundException; remaining name 'java:comp'
>> >> >>> >
>> >> >>> > I posted this issue in stackoverflow where I have the full
>> >> >>> > exception
>> >> >>> > and
>> >> >>> > my
>> >> >>> > jetty.xml configuration file.
>> >> >>> >
>> >> >>> > Thanks for the help!
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > http://stackoverflow.com/questions/30272184/cannot-deploy-a-wab-in-osgi-jetty-9-because-of-javax-naming-namenotfoundexceptio
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> >
>> >> >>> > _______________________________________________
>> >> >>> > jetty-users mailing list
>> >> >>> > jetty-users@xxxxxxxxxxx
>> >> >>> > To change your delivery options, retrieve your password, or
>> >> >>> > unsubscribe
>> >> >>> > from
>> >> >>> > this list, visit
>> >> >>> > https://dev.eclipse.org/mailman/listinfo/jetty-users
>> >> >>>
>> >> >>
>> >> >> _______________________________________________
>> >> >> jetty-users mailing list
>> >> >> jetty-users@xxxxxxxxxxx
>> >> >> To change your delivery options, retrieve your password, or
>> >> >> unsubscribe
>> >> >> from
>> >> >> this list, visit
>> >> >> https://dev.eclipse.org/mailman/listinfo/jetty-users
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Jan Bartel <janb@xxxxxxxxxxx>
>> >> > www.webtide.com
>> >> > 'Expert assistance from the creators of Jetty and CometD'
>> >>
>> >>
>> >>
>> >> --
>> >> Jan Bartel <janb@xxxxxxxxxxx>
>> >> www.webtide.com
>> >> 'Expert assistance from the creators of Jetty and CometD'
>> >> _______________________________________________
>> >> jetty-users mailing list
>> >> jetty-users@xxxxxxxxxxx
>> >> To change your delivery options, retrieve your password, or unsubscribe
>> >> from this list, visit
>> >> https://dev.eclipse.org/mailman/listinfo/jetty-users
>> >
>> >
>> >
>> > _______________________________________________
>> > jetty-users mailing list
>> > jetty-users@xxxxxxxxxxx
>> > To change your delivery options, retrieve your password, or unsubscribe
>> > from
>> > this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>>
>>
>> --
>> Jan Bartel <janb@xxxxxxxxxxx>
>> www.webtide.com
>> 'Expert assistance from the creators of Jetty and CometD'
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/jetty-users
--
Jan Bartel <janb@xxxxxxxxxxx>
www.webtide.com
'Expert assistance from the creators of Jetty and CometD'
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users