Thomas, It’s up to Aries team if blueprint will be supported or not under these platforms. So far Fuse/RedHat staff which are part of Aries team was so kind and they have added support for blueprint-noosgi environment which allows to run Aries under tomcat and other non-osgi environments. As it remains in main development branch for this project I suppose it is somehow supported by project team.
Kind regards, Łukasz Dywicki -- l...@code-house.org Twitter: ldywicki Blog: http://dywicki.pl Code-House - http://code-house.org Wiadomość napisana przez Thomas Diesler <thomas.dies...@jboss.com> w dniu 11 cze 2014, o godz. 11:32: > Blueprint will likely not be supported in Tomcat/WildFly > > —thomas > > On 10 Jun 2014, at 18:00, Krzysztof Sobkowiak <krzys.sobkow...@gmail.com> > wrote: > >> Hi >> >> Are we really going to let die the Spring integration with OSGi? I know this >> is rather a question for Karaf community. It would be good idea to resurect >> spring dm (as a new project?). We have Aries blueprint and, I think so, we >> don't need a big integration with Spring including next blueprint >> implementation. But it would be nice to have a good (extension to Aries?) >> integration allowing registering Spring beans in Osgi registry and working >> with no issues when communixating with blueprint bundles >> >> Best regards >> Krzysztof >> >> On Jun 5, 2014 10:10 AM, "Henryk Konsek" <hekon...@gmail.com> wrote: >>> Taking of the Red Hat, then I think with fabric8 and poly container, >>> that we are back being able to support Spring users fully again. >> >> Yeah, the next big thing I'm interested in is support for Vert.x >> container. That would be pretty cool alternative for Spring. Because >> honestly I don't find Blueprint as a real Spring competitor ;) . And >> BTW Vert.x is blessed by Red Hat, so having it as a first class >> container will make some people happy ;) . >> >>> I do not think we should turn away the fact that spring-dm is a dead >>> project, and that whatever spring osgi stuff happening at Eclipse is >>> going nowhere either. So basically spring on OSGi is going to be >>> tougher and tougher. >> >> Actually many people are surprised when I explain to them that Spring >> DM is not really maintained anymore. I think that Fuse documentation >> creates some confusion here, because we say there that Spring DM is >> supported by us, provide examples, etc. It will be nice to have a >> section in Fabric8 documentation that will make it clear that Spring >> DM is not a way to go anywhere. >> >> BTW I created issue [1] for myself on this topic. >> >> Cheers. >> >> [1] https://github.com/fabric8io/fabric8/issues/1634 >> >> -- >> Henryk Konsek >> http://henryk-konsek.blogspot.com >> >> -- >> You received this message because you are subscribed to the Google Groups >> "fabric8" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to fabric8+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "fabric8" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to fabric8+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >
