|Equinox for an enterprise environment [message #102043]
||Thu, 29 November 2007 03:20
Originally posted by: maus.pirack.com|
We are looking for a way to enrich our jboss appserver by adding a osgi
My knowledge on osgi is still very limited, thus I try to explain what we
are up to.
We are running a JBoss cluster environment with at least 10 nodes in the
The deployed applications ( packages ) are either ear files or war files.
We have reached a point where access to versioned services becomes
mandatory. SOAP is no choice for us as it eats performance in our case.
My question is ..
Has anyone experience in setting up equinox on the server side and allow
for things like:
-> ear deployment
-> binding to a jboss application server
Thanks for your help ...
|Re: Equinox for an enterprise environment [message #102300 is a reply to message #102043]
||Sun, 02 December 2007 14:07
| Simon Kaegi
Registered: July 2009
The Servletbridge as sefinitely been test with JBoss and works well.
For clustering one thing to be careful of is Session information. The app
servers will only be able to distribute session objects that are visible in
the web application. What this means is that if clustering is potentially
going to be important you should restrict your session objects to those that
come from the frameworks parent class loader. In most cases this is going to
be either the "boot" or "app" class loader. If you need to cluster some
application classes you should place the in your web apps WEB-INF/lib
directory and expose them either by creating a framework extension bundle or
by adding the java packages you need to the "extendedFrameworkExports"
init-param in the servletbridge. Sorry if this seems a bit confusing, but if
you can give a concret example I can help you work through it.
EAR deployment works fine, but what can get complext is accessing your EJBs.
You will need to expose the relevant interfaces using
extendedFrameworkExports ans settup your InitialContext can be a bit tricky.
From what I've seen most JNDI lookups are using the Context Class Loader to
scope the InitialContext. To get your EJB access to work correctly you will
have to find a way to get the Web Apps classloader and set that as your
Context Class Loader prior to creating your InitialContext. One fairly easy
way to get the Web Apps Classloader is to access it from the BridgeServlet.
e.g. BridgeServlet.class.getClassLoader(). I've worked through these
problems to get things working on Websphere but have not tried them with
JBoss. EJB access is a bit of a new area and any experience reports would be
very helpful here.
"Thorsten Maus" <firstname.lastname@example.org> wrote in message
> We are looking for a way to enrich our jboss appserver by adding a osgi
> My knowledge on osgi is still very limited, thus I try to explain what we
> are up to.
> We are running a JBoss cluster environment with at least 10 nodes in the
> cluster. The deployed applications ( packages ) are either ear files or
> war files.
> We have reached a point where access to versioned services becomes
> mandatory. SOAP is no choice for us as it eats performance in our case.
> My question is ..
> Has anyone experience in setting up equinox on the server side and allow
> for things like:
> -> clustering
> -> ear deployment
> -> binding to a jboss application server
> Thanks for your help ...
Powered by FUDForum
. Page generated in 0.07412 seconds