Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Http Whiteboard implementation over Tomcat 8

I you are using PDE projects then you can just use this repository as normal.

IF you are using bndtools >=3.3 you can use this repository configuration:

-plugin.Eclipse.Neon: \
    aQute.bnd.repository.p2.provider.P2Repository; \
        name                =   "Eclipse 4.6 (Neon)"; \
        url                 =   "http://download.eclipse.org/eclipse/updates/4.6/R-4.6-201606061100/"

In order to use this bundle with your own servlet container you must create a bundle which will create an instance of

org.eclipse.equinox.http.servlet.HttpServiceServlet

That instance must provide access to a ServletContext of the real servlet container, and from there the implementation will take over handling sub servlet context's for you.

Furthermore, I really dislike how this is implemented, It's a pretty terrible API design. It would be great to make this service oriented. I'll certainly appreciate any contributions to make it better.

- Ray


On Wed, Oct 26, 2016 at 2:46 PM, Todor Boev <rinsvind@xxxxxxxxx> wrote:
Hello,

I am looking for an implementation of the Http Whiteboard OSGi standard (Chapter 140 EEG spec). 
I also need to run it over Tomcat 8.
Finally it is preferable that the whiteboard runs in "native mode" rather than via a bridge servlet. I.e. have Tomcat instantiate an actual ServletContext for every web app root as it does with WAR/WABs.

Equinox supposedly has an Http whiteboard R6 implementation, but I am somewhat confused as to which bundles do I need to run to get it.

Regards
Todor

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev



--
Raymond Augé (@rotty3000)
Senior Software Architect Liferay, Inc. (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)

Back to the top