Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 23721 invoked from network); 3 Mar 2007 07:38:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Mar 2007 07:38:30 -0000 Received: (qmail 37680 invoked by uid 500); 3 Mar 2007 07:38:38 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 37152 invoked by uid 500); 3 Mar 2007 07:38:37 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 37141 invoked by uid 99); 3 Mar 2007 07:38:37 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 23:38:37 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jason.dillon@gmail.com designates 64.233.162.225 as permitted sender) Received: from [64.233.162.225] (HELO nz-out-0506.google.com) (64.233.162.225) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2007 23:38:25 -0800 Received: by nz-out-0506.google.com with SMTP id j2so1099264nzf for ; Fri, 02 Mar 2007 23:38:04 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=gNz6AIqMKFMSNP17A3caZ5VfJspj/ww+RHvfDNMuCDg69lNrx4jdNFgRRZbLsVt3DJtmOhfD24bfMv5ePt5qs1RyIO5LFp8a3pGeaWifDR5D0NvjGdh1odPM2nfVU76fkz560/4BQz1VCnVSkYd6D/qn4shr+aI5vuLkDhdnhPA= 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=PFai+MV9Ol53QAg5T0zl0Kgen45G3dda+7eTbFtLFkqdW75p8DNAT+Kp/4+GxKtzG+Oy4xzxf4TS/8LfkAACfIpYVOXXLabgM88/2D5HD3EpcSOU6mtNzE6eA+mJz2qYlkDV/dSct0v2/fO0BZUwfu4JsvpRhxV1exaYQo5d50I= Received: by 10.35.57.5 with SMTP id j5mr7959811pyk.1172907484356; Fri, 02 Mar 2007 23:38:04 -0800 (PST) Received: from ?10.0.1.2? ( [24.7.69.241]) by mx.google.com with ESMTP id y78sm6617942pyg.2007.03.02.23.38.03; Fri, 02 Mar 2007 23:38:03 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <09A752BF-7A05-40C7-B397-F4D29FFC4FF8@planet57.com> References: <55C60C42-1F22-43EF-8FD6-681E68F3FC02@planet57.com> <9EF83EC8-DA0C-430C-9729-F1F8C1F39EFB@yahoo.com> <09A752BF-7A05-40C7-B397-F4D29FFC4FF8@planet57.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jason Dillon Subject: Re: Upgrade Pluto to 1.1? (was Re: What are we using Castor for?) Date: Fri, 2 Mar 2007 23:38:01 -0800 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.752.3) Sender: Jason Dillon X-Virus-Checked: Checked by ClamAV on apache.org Actually, what I'd really like to see is our console allow app developers to plugin their own portlets for custom administration of their applications which are running in Geronimo... --jason On Mar 2, 2007, at 11:27 PM, Jason Dillon wrote: > 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: >> >> >> 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! >> >> >> >> 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 >> >> >> >