Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
To: commons-dev@jakarta.apache.org
From: Vic Cekvenich <cekvenich_vic@baseBeans.com>
Subject: Re: [docs] Crappy build system
Date: Wed, 13 Aug 2003 08:29:58 -0400
Lines: 112
Message-ID: <bhdb0a$m63$1@sea.gmane.org>
References: <bhc1el$9j$1@sea.gmane.org>
 <OF4349F068.FA2D86BA-ONCA256D81.00073650-CA256D81.0007BF43@multitask.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
In-Reply-To: 
 <OF4349F068.FA2D86BA-ONCA256D81.00073650-CA256D81.0007BF43@multitask.com.au>
Sender: news <news@sea.gmane.org>

Database makes it easy to mananage. (This runs on pgSQL, which is free)
Web app makes it easy to edit, via a browser you can cut/paste etc.

Somce kind of CMS would help, and bP's goal is to be the simplest CMS 
out there.
Look at Zope, Plone, PHP-Nukes.. etc.

bP is based on Struts and Tomcat 5. It goes w/ the dogdoof concept.

I could do a demo to anyone how easy it is to manage content w/it. (also 
  there is an avi video in the docs).

Static pages are not static.... they change from time to time, and CMS 
makes it easy.
.V


dion@multitask.com.au wrote:
> Do we really need a webapp and database for static content?
> --
> dIon Gillard, Multitask Consulting
> Blog:      http://blogs.codehaus.org/people/dion/
> 
> 
> news <news@sea.gmane.org> wrote on 13/08/2003 10:40:49 AM:
> 
> 
>>One way to maintain Jakarta web sites, such as commons, of course is to 
>>use a CMS system.
>>Store XML in a database (such as PostgreSQL), and edit remotely, flag as 
> 
> 
>>approved, have it pre-render to HTML, and have a jSTL emit it. Since 
>>content is in DB, it is easy to manager. Since it's a web app, it is 
>>easy to modify. Of course, ver fast.
>>Here is one example of Open Source CMS w/ a working URL:
>>http://basicportal.com/do/cmsPg?content=DEVELOPMENT
>>
>>See the url?
>>This makes a call to db to retrieve this content where = "DEVELOPMENT".
>>(Of course DB is cached auto by DAO so no ping if no change)
>>Realy, change the web site is easy, it's a lot like Wiki, except it has 
>>J2EE JDBC realms as to who can author and who can approve.
>>
>>.V
>>
>>
>>Craig R. McClanahan wrote:
>>
>>
>>>On Mon, 11 Aug 2003, Glenn Nielsen wrote:
>>>
>>>
>>>
>>>>Date: Mon, 11 Aug 2003 21:56:46 -0500
>>>>From: Glenn Nielsen <glenn@mail.more.net>
>>>>Reply-To: Jakarta Commons Developers List 
> 
> <commons-dev@jakarta.apache.org>
> 
>>>>To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
>>>>Subject: Re: [docs] Crappy build system
>>>>
>>>>Henri Yandell wrote:
>>>>
>>>>
>>>>>Jakarta Commons build system for the website is very very crappy.
>>>>>Regardless of whether things move to Maven or some other look and 
> 
> feel,
> 
>>>>>I'd like to check in the jars needed so that people don't have to go
>>>>>around hunting in jakarta-velocity, jakarta-site2 and who knows where
>>>>>else.
>>>>>
>>>>>Is anyone against this? Is there some reason for the current 
> 
> confusing
> 
>>>>>setup?
>>>>>
>>>>
>>>>-1 to checking the jars into CVS
>>>
>>>
>>>Agreed.  Changing the site generaton process to use Maven would 
> 
> eliminate
> 
>>>any need for this.
>>>
>>>Of course, so would using standard XML technologies like XSLT, but I'm 
> 
> not
> 
>>>going to volunteer to maintain the Commons site sources, so I'm not 
> 
> going
> 
>>>to go there :-).
>>>
>>>Craig
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>>
> 
> 


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