Re: The future of the Spring with Fabric8

[Krzysztof Sobkowiak <kr...@gmail.com>]

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" <he...@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+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

Re: The future of the Spring with Fabric8

[Henryk Konsek <he...@gmail.com>]

Just my two cents on Spring+OSGi :)

Spring DM isn't the way the modern Spring applications are supposed to
look like. It was good for Spring 2.x and early 3.x . Spring Boot and
Spring Data are becoming the Spring mainstream. The XML configuration
is officially not recommended anymore by Spring guys. Pivotal has
officially shown the middle finger to the OSGi. Try to run the
bleeding-edge Spring Boot + Spring Data using Spring DM - good luck
with it ;) .

I personally see no point in reanimating Spring DM. Let's face it -
Spring Boot with all its classpath magic won't ever work well in OSGi.
And Spring Boot is the future of Spring. I've seen too many people
crying their eyes out because of the Spring+OSGi rough edges to
believe that this is the right way of using Spring.

-1 for Spring in OSGi
+1 for Spring deployed to non-OSGi containers and managed by Fabric8

Cheers.

On Thu, Jun 12, 2014 at 4:48 PM, Łukasz Dywicki <lu...@code-house.org> wrote:
> 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
> --
> luke@code-house.org
> Twitter: ldywicki
> Blog: http://dywicki.pl
> Code-House - http://code-house.org
>
> Wiadomość napisana przez Thomas Diesler <th...@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 <kr...@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" <he...@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+unsubscribe@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+unsubscribe@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>
>



-- 
Henryk Konsek
http://henryk-konsek.blogspot.com

Re: The future of the Spring with Fabric8

[Łukasz Dywicki <lu...@code-house.org>]

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
--
luke@code-house.org
Twitter: ldywicki
Blog: http://dywicki.pl
Code-House - http://code-house.org

Wiadomość napisana przez Thomas Diesler <th...@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 <kr...@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" <he...@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+unsubscribe@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+unsubscribe@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 

Re: The future of the Spring with Fabric8

[Thomas Diesler <th...@jboss.com>]

Blueprint will likely not be supported in Tomcat/WildFly

—thomas

On 10 Jun 2014, at 18:00, Krzysztof Sobkowiak <kr...@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" <he...@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+unsubscribe@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+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Re: The future of the Spring with Fabric8

[Matt Sicker <bo...@gmail.com>]

Really, the only part of Spring I would still want in Karaf is the ability
to run Spring as bundles. I already use Blueprint files instead of Spring
beans files, so that's not an issue.


On 10 June 2014 11:00, Krzysztof Sobkowiak <kr...@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" <he...@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+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> >
>



-- 
Matt Sicker <bo...@gmail.com>