|
|
| Re: JBoss AS drops OSGI support [message #1232072 is a reply to message #1231691] |
Thu, 16 January 2014 01:35   |
Eclipse User |
|
|
|
Franck Mising name wrote on Wed, 15 January 2014 09:00Interesting reading: https://community.jboss.org/thread/229889
It seems that a Virgo server built around TomEE rather than tomcat would be the only open source container supporting both OSGI and Java EE... how hard would this be?
Geronimo and Glassfish both have (enterprise) OSGi support, and while JBoss does not bundle this support any more, it's still available as an add-on.
Having said that, Virgo is still about the closest thing to a "Spring application
server" that I know of, allowing you to write full fledged Spring-based (or blueprint-based if you prefer) enterprise applications while also enabling you to integrate and use JEE components like JPA. Not that it's impossible in other servers, they can also be extended with Gemini blueprint but in Virgo this is native while other servers make you jump through some hoops both when you're integrating this support and later each time you're deploying your applications.
So IMHO, the direction Virgo went for with Virgo Nano is really good - making a minimal extendable core is a great foundation to build a full, modular Blueprint/Spring/JEE server. Easier said than done unfortunately - although the effort shouldn't be too great, it's hard to find developers to do that without some serious commercial backing.
|
|
|
| Re: JBoss AS drops OSGI support [message #1232115 is a reply to message #1232072] |
Thu, 16 January 2014 04:07 |
| Eclipse User |
|
|
|
|
Yes, if you need Blueprint+Spring+Java EE Web Profile, then it would be necessary to build a hybrid of Virgo Nano Web (notably with its clever class loading scheme for Java EE) and the Virgo Kernel (for its Blueprint+Spring support). Essentially, this would be "just" a new Virgo packaging. But as you say, this would require some investment.
|
|
|
Powered by
FUDForum. Page generated in 0.03005 seconds
Home