<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - SpringSource to move dmServer to Eclipse – OSGi not ready for mainstream?</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Thu, 20 Jun 2013 04:16:19 -0400</pubDate>


    <item>

        <title>SpringSource to move dmServer to Eclipse – OSGi not ready for mainstream?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[I think it's good that Spring will hand this code over to Eclipse, if Eclipse accepts it.<br/><br/>Which they shouldn't.<br/><br/>As someone who watched the development of Spring's OSGI offerings from day one, I was exceptionally disappointed with how...]]></description>
        

        <pubDate>Wed, 28 Apr 2010 11:43:14 -0400</pubDate>

        

        <jf:creationDate>Fri, 16 Apr 2010 11:18:03 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 28 Apr 2010 11:43:14 -0400</jf:modificationDate>
        <jf:date>Apr 28, 2010</jf:date>
        <jf:author>yuregininsesi</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: SpringSource to move dmServer to Eclipse – OSGi not ready for mainstream?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[Happy Admiran has come this far in his career. I am hoping to ge my hands my server so i can upgrade to Eclipse]]></description>
        

        <pubDate>Sat, 30 Jan 2010 17:59:05 -0500</pubDate>

        

        <jf:creationDate>Thu, 28 Jan 2010 17:39:20 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 30 Jan 2010 17:59:05 -0500</jf:modificationDate>
        <jf:date>Jan 30, 2010</jf:date>
        <jf:author>mike jones</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>JavaEE not ready for OSGi or any change for that matter</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[After reading all the responses here I can only come to the conclusion that the Enterprise Java people are not ready for OSGi, not the other way around. They want to keep their flat, monolithic classpath and cruel API designs. They want complex build...]]></description>
        

        <pubDate>Fri, 29 Jan 2010 02:23:35 -0500</pubDate>

        

        <jf:creationDate>Fri, 29 Jan 2010 02:23:35 -0500</jf:creationDate>
        <jf:modificationDate>Fri, 29 Jan 2010 02:23:35 -0500</jf:modificationDate>
        <jf:date>Jan 29, 2010</jf:date>
        <jf:author>John Woo</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: SpringSource to move dmServer to Eclipse – OSGi not ready fo</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[We need objects, components versioning ? Not .jar versioning ?...]]></description>
        

        <pubDate>Sat, 23 Jan 2010 07:11:56 -0500</pubDate>

        

        <jf:creationDate>Sat, 23 Jan 2010 07:11:56 -0500</jf:creationDate>
        <jf:modificationDate>Sat, 23 Jan 2010 07:11:56 -0500</jf:modificationDate>
        <jf:date>Jan 23, 2010</jf:date>
        <jf:author>Erik GOLLOT</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Dependency Hell</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote>So just give me that advantage without making me do so much work to get my own jars running. I'm free to pick whatever versions I want for the jars I use in my app. I don't really need all that attention to OSGi details.</blockquote>...]]></description>
        

        <pubDate>Wed, 20 Jan 2010 09:34:17 -0500</pubDate>

        

        <jf:creationDate>Wed, 20 Jan 2010 09:34:17 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 20 Jan 2010 09:34:17 -0500</jf:modificationDate>
        <jf:date>Jan 20, 2010</jf:date>
        <jf:author>James Watson</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: OSGi not ready, is it?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[</blockquote>We've developed a complete enterprise SOA platform based on OSGi. Check out WSO2 Carbon project and the related products in <a hreft="http://wso2.com/products">wso2.com/products</a></p></blockquote>...]]></description>
        

        <pubDate>Wed, 20 Jan 2010 05:45:42 -0500</pubDate>

        

        <jf:creationDate>Wed, 20 Jan 2010 05:45:42 -0500</jf:creationDate>
        <jf:modificationDate>Wed, 20 Jan 2010 05:45:42 -0500</jf:modificationDate>
        <jf:date>Jan 20, 2010</jf:date>
        <jf:author>michele michele</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Dependency Hell</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[As we use more 3rd party jars, their dependencies become more likely to conflict. We teeter across this high-wire pretty well because we have been doing it for a long time. That doesn't mean its the right way to do it. And it is only going to get worse...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 20:50:35 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 20:50:35 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 20:50:35 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Lee Meador</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Modularization is difficult</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[Seems we're saying the same things..  So not sure why the disagreement.  If you thought I meant OSGI was a silver bullet I didn't mean too (others have tried to sell it to me that way)..    I also didn't meant to imply that OSGi is completely useless.....]]></description>
        

        <pubDate>Tue, 19 Jan 2010 17:09:18 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 17:09:18 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 17:09:18 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Gary P</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Re: Modularization is difficult</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote>I never claimed it did magic (though having read the spec some of it does seem magical! :-))   Not sure why fans of a particular technology have to be so insulting when people ask honest questions..</blockquote>...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 16:39:39 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 16:39:39 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 16:39:39 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>James Watson</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Re: Modularization is difficult</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote>You can change the manifests on 3rd party jars too.  I don't really see what difference it makes.  You don't need the source to modify exports in the manifest.  The point of OSGi is not to force people to use shitty APIs.  The point is that...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 16:06:57 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 16:06:57 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 16:06:57 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Gary P</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>OSGi not ready, is it?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote>I've never used OSGi on my projects because it is too complex to use and configure.<br>Many people thought that EJB 2.1 were too complex, and decided to migrate to the Spring approach.<br>Now, OSGi could die for the same reason.</blockquote>...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 12:37:42 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 12:37:42 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 12:37:42 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Sameera Jayasoma</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Modularization is difficult</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote><blockquote>Mainly the export.  By implicitly hiding what isn't exported you can prevent packages that are not part of the public API from being accessed.  This has a side benefit of determining structuring package easier.  You can have...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 10:58:36 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 10:58:36 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 10:58:36 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>James Watson</jf:author>
        <jf:replyCount>5</jf:replyCount>
    </item>


    <item>

        <title>Re: SpringSource to move dmServer to Eclipse – OSGi not ready for mainstream?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[Very interesting ... from Adrian's blog:...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 10:32:31 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 10:32:31 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 10:32:31 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Phil Zoio</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: SpringSource to move dmServer to Eclipse – OSGi not ready fo</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[Wow, people seem to have very strong feelings about this. Just to add a little bit of pro-OSGi feedback here....]]></description>
        

        <pubDate>Tue, 19 Jan 2010 10:11:37 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 10:11:37 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 10:11:37 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Joerg Bullmann</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Modularization is difficult</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=59183</link>

        

        
            <description><![CDATA[<blockquote>Mainly the export.  By implicitly hiding what isn't exported you can prevent packages that are not part of the public API from being accessed.  This has a side benefit of determining structuring package easier.  You can have public classes...]]></description>
        

        <pubDate>Tue, 19 Jan 2010 10:11:29 -0500</pubDate>

        

        <jf:creationDate>Tue, 19 Jan 2010 10:11:29 -0500</jf:creationDate>
        <jf:modificationDate>Tue, 19 Jan 2010 10:11:29 -0500</jf:modificationDate>
        <jf:date>Jan 19, 2010</jf:date>
        <jf:author>Gary P</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>



</channel>
</rss>

