We based some of our code on the server side on
JRoller... but why it is important as it
implements blog standards so it works with any compliant blog clients?
Regarding using the CMS rather than a portlet: of
course you can just deploy any JSR168 blogging
portlet (if you know one) but why deploying a CMS
within a CMS? Jahia already integrates all the
feature of a CMS (versioning, searching,
filtering, editing, DB persistance,...) so why
recreating everything within a portlet to manage
blog entries (= globally a simple jahia
containerlist)? Portlets are usueful if you want
to manage information with a lot of complex
business logic which are not indicated to be
directly managed by a portlet (eg: a timesheet
which would need to calculate hours, a
webclipping utility which need to parse/extract
data from another site, a chat portlet, a bridge
portlet towards MS Exchange, etc...)
Stéphane
At 00:03 17.02.2006, Leonard Sitongia wrote:
What is your blog software in 5.0 beta? Looks like Pebble?
In order to understand the architecture better,
I am wondering why it is a container of page
type instead of a portlet or webapp?
--
==Leonard E. Sitongia
Web Engineering Group
Scientific Computing Division
National Center for Atmospheric Research
P.O. Box 3000 Boulder CO 80307 USA
[EMAIL PROTECTED] voice: (303)497-2454 fax: (303)497-1804
