Was anyone able to solve this issue with a bundle fragment that adds the require-capability?
On Friday, September 30, 2016 at 2:47:34 AM UTC-4, Pavel wrote: > > The problem with runtime exception was solved by adding > Require-Capability: > osgi.extender;filter:="(osgi.extender=osgi.serviceloader.processor)",osgi.serviceloader;filter:="(osgi.serviceloader=javax.websocket.server.ServerEndpointConfig$Configurator)";resolution:=optional;cardinality:=multiple > > to manifest of javax.websocket-api.jar. > > However, in MyConfigurator class http session is always null. > > So, the question is the same - is the matter in PAX-WEB? > > Best, regards > -- -- ------------------ 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.
