Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of jason.dillon@gmail.com
 designates 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
        b=N6A4vIOZPaxPgXvlvpWLL8dNaOEhi2x5JA4XXhBMM8szO3MLuyO7n+pMhJBpDE8B/3dDSrZHA59dVli3LeniY1+aGp2r9hdG7PiWkoVFS/efsPWnzsT0siPTIs3Vb3GE1pDc5Bs6kSiJPW9kSk0DrqFDUzid6BZZrzZVeW9ak7o=
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <BF9A0C01-5985-4737-9CA0-A66AA5AAA0B8@planet57.com>
References: <55C60C42-1F22-43EF-8FD6-681E68F3FC02@planet57.com>
 <9EF83EC8-DA0C-430C-9729-F1F8C1F39EFB@yahoo.com>
 <BF9A0C01-5985-4737-9CA0-A66AA5AAA0B8@planet57.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <09A752BF-7A05-40C7-B397-F4D29FFC4FF8@planet57.com>
Content-Transfer-Encoding: 7bit
From: Jason Dillon <jason@planet57.com>
Subject: Re: Upgrade Pluto to 1.1? (was Re: What are we using Castor for?)
Date: Fri, 2 Mar 2007 23:27:04 -0800
To: dev@geronimo.apache.org
Sender: Jason Dillon <jason.dillon@gmail.com>

Or... what about Jetspeed 2?  Again I know jack about all things  
portal so I have no idea... but I would like to have the console get  
to be more pluggable and dynamic to install plugin bits at runtime.

--jason


On Mar 2, 2007, at 10:52 PM, Jason Dillon wrote:

> On Feb 13, 2007, at 5:49 PM, David Jencks wrote:
>> It's used by pluto for the admin console.  No idea if more recent  
>> would work.
>>
>> We could upgrade pluto too if anyone has some time to investigate
>
> I wonder if anyone from the Pluto team would want to help with  
> that... looks like 1.1 is not compatible with 1.0.1... but also  
> looks like that might not be a bad thing:
>
> <snip>
> Pluto 1.1 introduces a new container architecture. If you are  
> embedding Pluto in your portal, realize that 1.1 is not binarily  
> compatible with Pluto 1.0.x.
>
> Pluto 1.1 aims to simplify the architecture in order to make it  
> more user and developer friendly. You should find Pluto 1.1 easier  
> to get started with, easier to understand, and easier to embed with  
> your portal. Your feedback regarding how far we've come is always  
> welcome on the user and developer mailing lists!
>
> </snip>
>
> I don't know much abort portal muck, so I can't really show how  
> much better 1.1 might be... but I know that there have been some  
> issues with the console asis now to get stuff like plugin porlets  
> installed dynamically... perhaps 1.1 can help solve some of these  
> issues?
>
> Anyone know?
>
> --jason
>
>
>