Comments on: What the OSGi Web Container means for dm Server http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/ The voice of SpringSource Sat, 20 Mar 2010 12:14:29 -0500 http://wordpress.org/?v=2.8.5 hourly 1 By: Adrian Colyer http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167479 Adrian Colyer Thu, 02 Jul 2009 14:25:16 +0000 http://blog.springsource.com/?p=2087#comment-167479 @petev The RFC 66 implementation is usable standalone as per Rob's previous blog entry http://blog.springsource.com/2009/05/27/introduction-to-the-osgi-web-container/. The SpringSource implementation embeds Tomcat, but it would not surprise me to see other implementations based on Jetty being implemented elsewhere too. The RFC 66 project is hosted in SpringSource repos alongside all of our other OSGi-related projects, and there are no current plans to move any of these to Eclipse. Regards, Adrian. @petev

The RFC 66 implementation is usable standalone as per Rob's previous blog entry http://blog.springsource.com/2009/05/27/introduction-to-the-osgi-web-container/.

The SpringSource implementation embeds Tomcat, but it would not surprise me to see other implementations based on Jetty being implemented elsewhere too.

The RFC 66 project is hosted in SpringSource repos alongside all of our other OSGi-related projects, and there are no current plans to move any of these to Eclipse.

Regards, Adrian.

]]> By: petev http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167478 petev Thu, 02 Jul 2009 13:53:28 +0000 http://blog.springsource.com/?p=2087#comment-167478 Hi, looks very good! Is this going to be usable standalone and also with Jetty? Any plans to contribute it later to Equinox Runtime Project? 10x & greetings! Hi, looks very good! Is this going to be usable standalone and also with Jetty? Any plans to contribute it later to Equinox Runtime Project?

10x & greetings!

]]> By: Maven PAR Plugin 1.0.0.M1 | SpringSource Team Blog http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167396 Maven PAR Plugin 1.0.0.M1 | SpringSource Team Blog Wed, 24 Jun 2009 12:00:39 +0000 http://blog.springsource.com/?p=2087#comment-167396 [...] file can contain more than just JAR files. With the introduction of OSGi RFC 66, the dm Server has deprecated Web Modules in favor of the standard Web Container files using a .war extension.  Because of this, the PAR [...] [...] file can contain more than just JAR files. With the introduction of OSGi RFC 66, the dm Server has deprecated Web Modules in favor of the standard Web Container files using a .war extension.  Because of this, the PAR [...]

]]> By: Rob Harrop http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167203 Rob Harrop Thu, 04 Jun 2009 09:42:44 +0000 http://blog.springsource.com/?p=2087#comment-167203 @Daniel Web modules will be removed in 2.0 M3 to give users plenty of time to adjust. I just finished writing the migration guide yesterday. As for modular web apps and UI composition - we're starting work on that in our next sprint which starts on Monday. @Daniel

Web modules will be removed in 2.0 M3 to give users plenty of time to adjust. I just finished writing the migration guide yesterday.

As for modular web apps and UI composition – we're starting work on that in our next sprint which starts on Monday.

]]> By: Rob Harrop http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167202 Rob Harrop Thu, 04 Jun 2009 09:41:18 +0000 http://blog.springsource.com/?p=2087#comment-167202 @Anoop Personalities are definitely staying. We see the Web Container being one of the personalities exhibited by dm Server and to support this we are using the Web Container RI. @Anoop

Personalities are definitely staying. We see the Web Container being one of the personalities exhibited by dm Server and to support this we are using the Web Container RI.

]]> By: Daniel Rubio http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167184 Daniel Rubio Wed, 03 Jun 2009 17:44:33 +0000 http://blog.springsource.com/?p=2087#comment-167184 Thanks for all the answers. I only have a few more questions on time-lines. Adrian and Costin mention Spring-DM 2.0 as a target for leveraging RFC 66 (and deprecating web support as it currently stands in Spring-DM) What about dm Server, RFC 66 and the deprecation of web modules? Will this occur post-dm Server 2.0 final release ? or will it be present in dm Server 2.0 final release? Finally, will there be something on the UI composition front (e.g shared session state between fragments, JSF) to look at in dm Server 2.0 ? Or is this something beyond dm Server 2.0 final release? Thanks for all the answers.

I only have a few more questions on time-lines. Adrian and Costin mention Spring-DM 2.0 as a target for leveraging RFC 66 (and deprecating web support as it currently stands in Spring-DM)

What about dm Server, RFC 66 and the deprecation of web modules? Will this occur post-dm Server 2.0 final release ? or will it be present in dm Server 2.0 final release?
Finally, will there be something on the UI composition front (e.g shared session state between fragments, JSF) to look at in dm Server 2.0 ? Or is this something beyond dm Server 2.0 final release?

]]> By: Anoop http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167163 Anoop Tue, 02 Jun 2009 15:07:53 +0000 http://blog.springsource.com/?p=2087#comment-167163 Does this mean that the whole concept of personalities is going away from Spring DM Server or it is just the "Spring DM specific web module" personality being replaced by "OSGI specification based Web Container web bundle" ? Does this mean that the whole concept of personalities is going away from Spring DM Server or it is just the "Spring DM specific web module" personality being replaced by "OSGI specification based Web Container web bundle" ?

]]> By: Costin Leau http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167162 Costin Leau Tue, 02 Jun 2009 11:01:41 +0000 http://blog.springsource.com/?p=2087#comment-167162 Adding to what Adrian said, from a technical perspective, RFC 66 does all that Spring DM web support offers in a standard, portable way. In fact, I would expect existing web applications to migrate to RFC 66 with minimal (if any) updates. As for the roadmap the web support will be deprecated in the upcoming 2.0 and then removed in the next major version. We'll make sure to properly document the transition from one scenario to the other as well as migrate the samples included in the distribution. Adding to what Adrian said, from a technical perspective, RFC 66 does all that Spring DM web support offers in a standard, portable way. In fact, I would expect existing web applications to migrate to RFC 66 with minimal (if any) updates.
As for the roadmap the web support will be deprecated in the upcoming 2.0 and then removed in the next major version. We'll make sure to properly document the transition from one scenario to the other as well as migrate the samples included in the distribution.

]]> By: Adrian Colyer http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167160 Adrian Colyer Tue, 02 Jun 2009 10:25:23 +0000 http://blog.springsource.com/?p=2087#comment-167160 Spring DM 2.0 is focused on being the RI for the OSGi Blueprint Service (aka RFC 124). Now that web support in OSGi has its own fledgling spec (RFC 66) and its own project, the existing support in Spring DM will be deprecated in favour of integration with the RFC 66 web extender. Spring DM 2.0 is focused on being the RI for the OSGi Blueprint Service (aka RFC 124). Now that web support in OSGi has its own fledgling spec (RFC 66) and its own project, the existing support in Spring DM will be deprecated in favour of integration with the RFC 66 web extender.

]]> By: Rob Harrop http://blog.springsource.com/2009/06/01/what-the-osgi-web-container-means-for-dm-server/comment-page-1/#comment-167158 Rob Harrop Tue, 02 Jun 2009 06:59:37 +0000 http://blog.springsource.com/?p=2087#comment-167158 @Daniel The structure of a webbundle is currently in flux. If you take any old WAR and install it using the webbundle: URL scheme then, that webbundle is still a valid WAR. There is discussion about being able to create any old bundle and have it serve up web content, but I imagine that will still end up surprisingly WAR-like. The challenge of a new format is getting something that works nicely with tooling and also has a well-defined contract for resources that are intended to be private to the app - like WEB-INF. RFC66 only talks about what we call WARs, shared-library WARs and shared-service WARs. It provides headers to control the context path and where the container extracts JSP content to. I liked the generation capabilities of web modules but too many people found them confusing, and as you say, they don't really scale when you have a large project. There is nothing to prevent us from supporting generation on dm Server by extending our RFC66 contract but I'd like to be certain that what we support has real concrete value. Re: web support in Spring DM. I'm not 100% certain on the plan there. I'll check with Adrian/Costin and they can weigh in. @Daniel

The structure of a webbundle is currently in flux. If you take any old WAR and install it using the webbundle: URL scheme then, that webbundle is still a valid WAR. There is discussion about being able to create any old bundle and have it serve up web content, but I imagine that will still end up surprisingly WAR-like.

The challenge of a new format is getting something that works nicely with tooling and also has a well-defined contract for resources that are intended to be private to the app – like WEB-INF.

RFC66 only talks about what we call WARs, shared-library WARs and shared-service WARs. It provides headers to control the context path and where the container extracts JSP content to.

I liked the generation capabilities of web modules but too many people found them confusing, and as you say, they don't really scale when you have a large project. There is nothing to prevent us from supporting generation on dm Server by extending our RFC66 contract but I'd like to be certain that what we support has real concrete value.

Re: web support in Spring DM. I'm not 100% certain on the plan there. I'll check with Adrian/Costin and they can weigh in.

]]>