1:14 p.m.
Hi Folks,
I trying to optimize the JBoss OSGi HttpService integration with
JBossWeb. Currently this generates JBossWebMetaData in memory and
deploys that through the MainDeployer.
What I am looking for however is an embedded Http server that I can use
in the OSGi service. Most other HttpService implementations use Jetty
for that reason.
Is it possible to use JBossWeb embedded and setup Http endpoints through
an API?
cheers
-thomas
3:12 p.m.
On Thu, 2009-02-19 at 13:14 +0100, Thomas Diesler wrote:
Hi Folks,
I trying to optimize the JBoss OSGi HttpService integration with
JBossWeb. Currently this generates JBossWebMetaData in memory and
deploys that through the MainDeployer.
Why? More re-inventing the wheel?
It should be upto the jbossweb team whether they produce an osgi bundle
for standalone usage.
I could understand it if you were trying to implement the HTTPService
on top of JBossAS's TomcatService.
We already agreed along time ago that JBoss would provide a core
OSGi implementation/facade on top of the Microntainer/Deployers
that's where we should be putting our resources.
For the compendium (where it is not duplicated by JBossAS services
where we can provide a facade) we should work with other open source
OSGi implementations and share the implementations.
What I am looking for however is an embedded Http server that I can use
in the OSGi service. Most other HttpService implementations use Jetty
for that reason.
Is it possible to use JBossWeb embedded and setup Http endpoints through
an API?
Of course it is possible, what do you think the jbossas/tomcat
project does?
If you really want to do it from scratch
(I did it once to prove you could bootstrap Tomcat using the MC
inside a testcase) you'll find it very
annoying because it tends to just throw NPEs (and even worse eat
error messages) if you get the api usage wrong.
cheers
-thomas
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
3:41 p.m.
On Thu, 2009-02-19 at 15:12 +0100, Adrian Brock wrote:
We already agreed along time ago that JBoss would provide a core
OSGi implementation/facade on top of the Microntainer/Deployers
that's where we should be putting our resources.
For the compendium (where it is not duplicated by JBossAS services
where we can provide a facade) we should work with other open source
OSGi implementations and share the implementations.
By way of a more concrete example in this case.
If we used the equinox/eclipse compendium there would be no
need to deploy their "httpservice bundle"
which is a very old Tomcat-4.1.29
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tomcat/
In JBossAS if you asked the OSGi ServiceRegistry for the HTTPService
you would get back our "TomcatService" that implements it
(or maybe some other bean that delegates to it?).
It shouldn't need the service to be actually packaged as an OSGi bundle.
The MC should already know that there is some MC context that implements
that service - like we do with in/uncallbacks.
Like I wrote in the osgi forum itself.
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131151
you should be able to use anything that JBoss controls as an osgi
service e.g. an ejb via its home or remote interface.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
5822
days inactive
5822
days old
jboss-development@lists.jboss.org
2 comments
2 participants
participants (2)
-
Adrian Brock -
Thomas Diesler