Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>
Mime-Version: 1.0 (Apple Message framework v618)
In-Reply-To: <DFELLFNEHCMNIPIBAAPGMEFODLAA.tim.reilly@consultant.com>
References: <DFELLFNEHCMNIPIBAAPGMEFODLAA.tim.reilly@consultant.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <BF1611D9-C6DC-11D8-88E3-000393C78E78@bluesunrise.com>
Content-Transfer-Encoding: 7bit
From: David Sean Taylor <david@bluesunrise.com>
Subject: Re: [J2] What's wrong with jcr [was: Menu Implementation]
Date: Fri, 25 Jun 2004 12:20:40 -0700
To: "Jetspeed Developers List" <jetspeed-dev@jakarta.apache.org>


On Jun 24, 2004, at 1:04 PM, Tim Reilly wrote:

> I had been asking some questions about jsr-170 and David Nuescheler 
> had sent
> me this link to their demo application of the jcr api's. I asked if I 
> could
> share with the jetspeed list, he agreed but wanted to _*emphasize*_ 
> the demo
> is Alpha and as well.. the specification in NOT final.
>
> He also quickly set up some portal related nodes types (not from the
> jetspeed discussions, but his own thoughts: pages and portlets, and 
> portlet
> under /myportal in the Content Browser)
> The demo url: http://jsr170tools.day.com
>
> I had begun to enter the node types discussed here (portal:folder,
> portal:fragment), but ran into a persistence error (par for the 
> course.)
> I'll try again later, but I wanted to share the url since it puts more
> 'concrete-ness' around this discussion. Of particular interest is the 
> Node
> Type administration, and the Content Browser.
>
The UI has potential although it did seem very buggy and un-responsive 
at times

Is this an open source based project or a reference implementation?


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org