Apache Felix OBR and the new Repoindex

["Bellinger, Matthew" <Ma...@saabsensis.com>]

I am attempting to create a system that will leverage the OBR concept in
Apache Felix.  From what I have read on the Apache Felix site, I should
be using 'bindex' to index my repository.  Unfortunately when I go to
the web site for bindex (http://www.osgi.org/Repository/BIndex) I find
that it has been recently replaced by 'repoindex'.  My attempts at using
repoindex have so far not been successful.  When I try to access the xml
that is generated by repoindex with the Apache Felix OBR Web Console
plugin, it fails to work.

 

It seems to fail on lines that have a directive tag inside of a
requirement tag, similar to:
<requirement namespace='osgi.ee'>

    <directive name='filter' value='(osgi.ee=J2SE-1.5)'/>    <!--Fails
on this line -->

</requirement>

 

With the following stack trace:

[295287971@qtp-605679902-5] WARN org.apache.felix.http.jetty -
/system/console/obr

javax.servlet.ServletException: Failed to add repository
file:///home/mbelling/obr/index.xml.gz: java.lang.Exception: Error while
parsing resource null at line 97 and column 60

      at
org.apache.felix.webconsole.plugins.obr.internal.FelixBundleRepositoryRe
nderHelper.doAction(FelixBundleRepositoryRenderHelper.java:137)

      at
org.apache.felix.webconsole.plugins.obr.internal.WebConsolePlugin.doActi
on(WebConsolePlugin.java:243)

      at
org.apache.felix.webconsole.plugins.obr.internal.WebConsolePlugin.doPost
(WebConsolePlugin.java:109)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

      at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiMan
ager.java:493)

      at
org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiMan
ager.java:418)

      at
org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(Serv
letHandler.java:96)

      at
org.apache.felix.http.base.internal.handler.ServletHandler.handle(Servle
tHandler.java:79)

      at
org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(Serv
letPipeline.java:42)

      at
org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFil
ter(InvocationFilterChain.java:49)

      at
org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(Ht
tpFilterChain.java:33)

      at
org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(Fil
terPipeline.java:48)

      at
org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatc
her.java:39)

      at
org.apache.felix.http.base.internal.DispatcherServlet.service(Dispatcher
Servlet.java:67)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

      at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)

      at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)

      at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)

      at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)

      at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)

      at org.mortbay.jetty.Server.handle(Server.java:326)

      at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)

      at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.j
ava:943)

      at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)

      at
org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)

      at
org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)

      at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:
410)

      at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java
:582)

 

Is there any work being done to match apache felix with the newest
repoindex?  If not, is there an archive someplace where I can get an
Apache Felix compatible version of bindex?

 

Thank you,

~Matt

-
This message is intended only for the addressee and may contain information that is company confidential or privileged.  Any technical data in this message may be exported only in accordance with the U.S. International Traffic in Arms Regulations (22 CFR Parts 120-130) or the Export Administration Regulations (15 CFR Parts 730-774). Unauthorized use is strictly prohibited and may be unlawful. If you are not the intended recipient, or the person responsible for delivering to the intended recipient, you should not read, copy, disclose or otherwise use this message. If you have received this email in error, please delete it, and advise the sender immediately. 
-