<?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 - Container Client Interface</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, 23 May 2013 03:05:01 -0400</pubDate>


    <item>

        <title>Not sure what value this adds?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[Makes sense.<br><br>If there was a sufficiently generic way to programmatically start up a container, I think that's the idea. Not all containers have ways to programmatically start the container. Not as easy as something like PicoContainer...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 17:20:20 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 17:20:20 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 17:20:20 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Steve Lewis</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Not sure what value this adds?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[<blockquote>Merlin *is* a container. The goal of CCI is simply to offer an API to start/stop *existing* containers. The goal is not to create another container nor it is to create an API for containers to write against (that would be Avalon, Pico/Nano,...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 16:48:25 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 16:48:25 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 16:48:25 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Nader Aeinehchi</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>RE: Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[<blockquote><blockquote>I'm assuming you're going to provide Ant tasks for this - and that its integration into Cactus will be transparent?  What I'd really like to see in the Ant tasks is that you can set the app server as a property - and easily switch...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 11:00:22 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 11:00:22 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 11:00:22 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Jason Carreira</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Not sure what value this adds?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[<blockquote>There are several container systems that are capable of managing the life-cycle of components(including containers).  For example, take a look at Apache Avalon Merlin that has a strong and flexible way of doing it.Have I totally misunderstood...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 09:15:34 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 09:15:34 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 09:15:34 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Vincent Massol</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Not sure what value this adds?</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[There are several container systems that are capable of managing the life-cycle of components(including containers).  For example, take a look at Apache Avalon Merlin that has a strong and flexible way of doing it.<br><br>Have I totally misunderstood...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 07:33:05 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 07:33:05 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 07:33:05 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Nader Aeinehchi</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[Yeah. I hadn't thought of that, but you're right. As long as the unit test can execute inside the container, and know it's started by the time the test executes, it doesn't really matter.<br><br>My personal preference is to have fewer steps, and I think...]]></description>
        

        <pubDate>Fri, 30 Jul 2004 07:27:39 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 07:27:39 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 07:27:39 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Steve Lewis</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[<blockquote>Bringing the container to the test, rather than bringing the test to the container (like Cactus).</blockquote>Exactly! That said Cactus does bring the container to the test... ;-) (with the &lt;cactus&gt; Ant task).]]></description>
        

        <pubDate>Fri, 30 Jul 2004 06:11:24 -0400</pubDate>

        

        <jf:creationDate>Fri, 30 Jul 2004 06:11:24 -0400</jf:creationDate>
        <jf:modificationDate>Fri, 30 Jul 2004 06:11:24 -0400</jf:modificationDate>
        <jf:date>Jul 30, 2004</jf:date>
        <jf:author>Vincent Massol</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[Very interesting. I did something fairly similar, starting up a JBoss MBeanServer in a JUnit test. Bringing the container to the test, rather than bringing the test to the container (like Cactus). I got the idea from Andrew Oliver, so it's not really my...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 18:12:21 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 18:12:21 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 18:12:21 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Steve Lewis</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>RE: Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[How would this compare to just leveraging something like OSGI 3.0++ from the eclipse 3.0 framework? Are you addressing class loaders, dependencies between components etc?<br><br>Thanks]]></description>
        

        <pubDate>Thu, 29 Jul 2004 16:27:24 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 16:27:24 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 16:27:24 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Billy Newport</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>RE: Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[<blockquote>I'm assuming you're going to provide Ant tasks for this - and that its integration into Cactus will be transparent?  What I'd really like to see in the Ant tasks is that you can set the app server as a property - and easily switch from using...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 15:05:37 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 15:05:37 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 15:05:37 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Vincent Massol</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>RE: Container Client Interface</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[I'm assuming you're going to provide Ant tasks for this - and that its integration into Cactus will be transparent?  What I'd really like to see in the Ant tasks is that you can set the app server as a property - and easily switch from using one server...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 14:34:44 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 14:34:44 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 14:34:44 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>mraible</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>should provide more than start/stop and deploy</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[I think such a project would be useful however there are some issues related to configuration and deplyoment which I still find annoying. Details can be found at the URL below. It would be nice if this project addresses some of these issues as...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 13:38:19 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 13:38:19 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 13:38:19 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>sjivan</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Container Client Interface - a contribution</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[Before everyone starts asking... :-)<br><br>1/ No, the goal of the CCI project is not to create yet another deployment API. There's already JSR77/88 for this. CCI is about providing an API to start/stop containers (including in-place startup).<br><br>2/...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 13:07:39 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 13:07:39 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 13:07:39 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Vincent Massol</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Container Client Interface - a contribution</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[This code does it, in part. I no longer maintain the package it's part of and would have no problem contributing it if it's at all useful.<br><br><a...]]></description>
        

        <pubDate>Thu, 29 Jul 2004 12:51:57 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 12:51:57 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 12:51:57 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Kyle Downey</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>oops</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=27669</link>

        

        
            <description><![CDATA[ervy = every one!<br><br>My typing is dreadful]]></description>
        

        <pubDate>Thu, 29 Jul 2004 12:11:27 -0400</pubDate>

        

        <jf:creationDate>Thu, 29 Jul 2004 12:11:27 -0400</jf:creationDate>
        <jf:modificationDate>Thu, 29 Jul 2004 12:11:27 -0400</jf:modificationDate>
        <jf:date>Jul 29, 2004</jf:date>
        <jf:author>Rob Harrop</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>



</channel>
</rss>

