Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ammulder@gmail.com designates
 66.249.92.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Tvy+LfZKZbq7Ou/ZVd95n5VHcr+gAuKdFkgR3TEtohbFxdk30McyPH/KWxc4TF37lAtlf0YzzPr81vWI0F/6PKgjMmZjmZ26KeMPuMZeA1ACZXdbMhcDn70BvxRa+YClo6aEbueMqjM5JNtJFQ7yIHnbOcQqfb35RWzUfi4xSww=
Message-ID: <74e15baa0601231911l1497d6b4jff163771b16f939b@mail.gmail.com>
Date: Mon, 23 Jan 2006 22:11:00 -0500
From: Aaron Mulder <ammulder@alumni.princeton.edu>
Sender: ammulder@gmail.com
To: Geronimo Dev <dev@geronimo.apache.org>
Subject: JMS Portlet Testing needed on HEAD and 1.0 Branch
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

All,

I just put in the start of the revised JMS portlet.  Currently it lets
you deploy a new JMS resource (or just show the plan) with connection
factories and/or destinations.  It does not yet let you view or edit
existing resources.

Anyway, please take it for a spin and let me know what you think.=20
It's the top portlet in the "JMS Resources" entry in the console (not
"JMS Server", and not the lower 2 portlets which are still the old
ones).  Note that you'll need a fresh SVN build as of just now.

Thanks,
    Aaron