Our current approach is also a "migration" strategy. This is an unfortunate 
reality for those with large existing code-bases.

We anticipate "flipping the architecture" soon which will put Everything in 
Karaf. The non-OSGI libraries will be collected together as a "legacy" bundle. 
At that point we'll be leveraging PAX-Web instead of deploying inside an 
existing servlet container.

-Nick

From: Serge Huber <[email protected]<mailto:[email protected]>>
Reply-To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Date: Wednesday, March 30, 2016 at 3:21 AM
To: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: Embedding Karaf in a WAR (Tomcat)

Hi Achim and Martin,

Actually my own company is going through this transition, but for the moment 
our main application (CMS) still has to be deployed within web containers such 
as Tomcat or WebSphere. So using an Http Bridge is a hard requirement for the 
moment.

As soon as we can drop this requirement we will but in the meantime we want a 
bridge that can be as feature-ful as possible. Currently we use the Felix Http 
Bridge in production but I’m really hoping we can switch to the new Pax Web 
Bridge soon, as it is a *lot* better.

Yes it is indeed strange to have this bridge because you can potentially have a 
web application within a web application (but at the same time this is kinda 
cool, ok I’m a nerd :)). Anyway, I believe it can be an interesting migration 
path for a lot of existing web applications out there.

Let’s get everyone on Karaf & Pax Web :) Who needs Node.js ? :)

cheers,
  Serge…


On 29 mars 2016, at 17:47, Achim Nierbeck 
<[email protected]<mailto:[email protected]>> wrote:

Hi Martin,

I'm still in favor of using plain Karaf with Web-Container instead of the 
opposite, but I can see the benefits for easier transition of doing the bridge 
thing. Thanks to the Help of Serge, we now have a special branch [1], cause the 
bridge is still work-in-progress [2].

regards, Achim

[1] - https://github.com/ops4j/org.ops4j.pax.web/tree/PAXWEB-606-Servlet-Bridge
[2] - https://ops4j1.jira.com/browse/PAXWEB-606

2016-03-29 16:45 GMT+02:00 mjelen 
<[email protected]<mailto:[email protected]>>:
Hi Serge,

thank you for your reply! I'll look into the PAX Web Bridge, I guess the
right place to talk about it is the OPS4J Google Group.

I admit I haven't thought of looking at PAX Web for my purpose because I'd
seen it as having the opposite purpose of what I'm looking for - that is,
starting an embedded Tomcat (or Jetty or Undertow) rather than running
inside a Tomcat instance. Especially since I've read several comments from
Achim dissuading people from embedding Karaf in Tomcat (which I can
understand, I'm not happy about it myself and I'll keep trying to get rid of
this requirement).

Regards
Martin



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Embedding-Karaf-in-a-WAR-Tomcat-tp4045931p4046031.html
Sent from the Karaf - User mailing list archive at 
Nabble.com<http://nabble.com>.



--

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & 
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master


Reply via email to