Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: =?gb2312?B?u8a6o7asuavLvtPKz+Q=?= <hhd@winspeed.cn>
To: <dev@cocoon.apache.org>
Subject: Re: How to get spring beans with Cocoon Template 1.0?
Date: Fri, 21 Nov 2008 11:43:44 +0800 (CST)
Message-ID: <F0C906BAE6084DF2B88D993B87373E89@HHD>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
Thread-Index: AclLi1i05H/+pCxISeyy9xDROuvhwA==

Hi,Thorsten Scherler

There's many reasons to do this in template,But the MOST IMPORTANT IS it's
quick and don't need to write java so it does not need to restart server.For
a developer who just know spring and common java,it's not easy to implement
cocoon's interface or any other specify interface even they are open source.
I am the only one who really understand cocoon in my entire group,the other
developers only follow my deployment guide to do the copy&paste&edit
work.Java?they only write the common java bean.

The complains above is about one problem:Cocoon is not so popular just like
Spring or even Hibernate(at least many people knows what it is),that many
java developers will study and undersand.So even better or great cocoon
implement exist ,much fewer people know.I admit it is not a good solution,my
groups also complain why then can't just add code in common java but in a
xml file,but the reality is it's the best way for the project now.

BTW,I think the better way to do this is to get appctx in flowscript and
send it to template with sendPage(url,{"appctx":attctx});

Regards,

Roy Huang