|ServletBridge Enterprise Ready? [message #722446]
||Mon, 05 September 2011 19:42
Registered: August 2011
I'm trying to understand and evaluate the servlet bridge and can't seem to find adequate feedback on servletbridge in practice. While the concepts of OSGI are great and address many problems in terms of portability of application code in a J2EE application server, I have some confusion on a couple things.|
1. Googling I've found two variations of the servletbridge project. The eclipse equinox implements a servlet which manages the OSGI environment under the application context root by default. I've found a version that uses a ServletFilter and several proposals of a servlet filter. Is there uncertainty on how exactly to implement the concept of the servlet bridge?
2. Using the servletbridge seems to make a lot of assumptions on resolving and manually starting up modules from a console. It seems to tightly couple the developer to their applications (not typical in J2EE large enterprise). Applications remain in "RESOLVED" state and need to be manually started up. Any proposals on how to force new bundles to autostart in bridgeservlet and how an application server administrator would manage an OSGI app?
Thanks, any feedback would be great.
P.S. Has anyone had any success on using the bridgeservlet in an enterprise application? I've had an opportunity to use IBM's JAZZ and they seem to incorporate OSGI into their application architecture (although now I think they have a hybrid architecture with REST, WebFragments, and OSGI).
Powered by FUDForum
. Page generated in 0.03822 seconds