-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 12 Jan 2006, Reinhard Poetz wrote:
Date: Thu, 12 Jan 2006 10:44:56 +0100 (CET)
From: Reinhard Poetz <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Block deployment: working with blocks from a user's point of view
--- Giacomo Pati <[EMAIL PROTECTED]> schrieb:
The first thing we need to have is the archetype for
a block skeleton to
get a step ahead through the first tutorial. So
let's define a list of
items we need and requirements one has.
If I understand your tutorials correctly [1] is
about creating a single
block (which _can_ be a single application or a
brick for build an
application)
yes, right
and [2] is the creation of a webapp/war
directory/file
deployable into a servlet engine. Is this correct?
yes
So the next tasks are
- creating the block archetype
(for the content see [1] "Create your block
skeleton")
Where should .xconf file be located so they will be included?
Do we need a different mechanism to include those (is copying over
to the Cocoon WEB-INF/xconf an option for rapid development)?
How can one ev. define logkit.xml stuff if they want to have their own
logging factory/target/category for the components defined in the block
(asuming logkit is still the main logging system in Cocoon)?
Same applies to stuff going into web.xmlof the context?
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDxquiLNdJvZjjVZARAmLnAKC3L1g0sxKSAVwX4q2QPNq8dSMlyACfbrrv
A6i6HSFop9L7TO3ROQHqZzs=
=lyFe
-----END PGP SIGNATURE-----
