|
|
|
|
Re: Blueprint Spring support [message #647841 is a reply to message #647804] |
Sun, 09 January 2011 21:14 |
|
I'm also sharing the OP concerns and more generally about Gemini Blueprint roadmap.
We have invested a lot in the excellent Spring Dynamic Modules for OSGi and use the 1.2.1 version (released one year ago) across all our projects.
We were very excited by Spring DM becoming an OSGi spec with Eclipse Gemini Blueprint its RI. But we are now slowly getting worried that the project is not really progressing toward a stable release.
Are we mistaken?
Is there still an interest for Spring/OSGi integration??
Argeo GmbH (Berlin) - http://www.argeo.org/
|
|
|
|
|
|
|
Re: Blueprint Spring support [message #648086 is a reply to message #648009] |
Tue, 11 January 2011 08:08 |
|
Costin Leau wrote on Mon, 10 January 2011 13:23 | As for the roadmap, Spring DM is a mature project (despite what some think about its numbering) - the fact that a specification was built on it shows it.
|
Spring DM is indeed mature and working very well (I wrote the version we use just for the sake of precision).
Actually we have problems only with its web deployment support and we would like to upgrade to Gemini Web. But we thought that we will do this in one go, with an update of Spring DM to Gemini Blueprint as well. Hence our wish for a stable release of the latter...
But take your time, as long as we know that the project is alive, we fully understand that "it will be ready when it is ready"!
Argeo GmbH (Berlin) - http://www.argeo.org/
|
|
|
|
Re: Blueprint Spring support [message #650555 is a reply to message #648015] |
Tue, 25 January 2011 14:14 |
Costin Leau Messages: 45 Registered: February 2010 |
Member |
|
|
Yes, we intend to track Blueprint as it evolves - the intention is of course to support both Blueprint and Spring programming model at the same time - assuming that's not the case, the former will take precedence of course.
David Erickson wrote on Mon, 10 January 2011 21:55 | Hi Costin-
Thanks for the reply. Please see inline-
Costin Leau wrote on Mon, 10 January 2011 13:23 |
Regarding Spring support - this will always be there as long as Blueprint will be based on Spring. Blueprint is a subset of Spring so removing the Spring support means either replacing the container or restricting the user from accessing it.
Both alternatives are unlikely for the foreseeable future.
|
The current case I fully understand, but almost inevitably Blueprint will eventually expand to include features that may not be covered directly by Spring, or could potentially even be in conflict, in this case I would assume you would just expand and build around the existing Spring code, but I wanted to understand if this is your intention?
Thanks,
David
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04769 seconds