Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Robby Pelssers <Robby.Pelssers@nxp.com>
To: "users@cocoon.apache.org" <users@cocoon.apache.org>
Date: Thu, 8 Mar 2012 22:26:47 +0100
Subject: RE: parent of parent artifact?
Thread-Topic: parent of parent artifact?
Thread-Index: Acz9b95Qahv99e8ERTKXhbBh3GE/OQAAjoBg
Message-ID: 
 <927C66C0775CCA43B88EB1E3006614B306541B21@eu1rdcrdc1wx032.exi.nxp.com>
References: <4F5786E1.1010308@sil.org>
 <927C66C0775CCA43B88EB1E3006614B3064A4C70@eu1rdcrdc1wx032.exi.nxp.com>
 <927C66C0775CCA43B88EB1E3006614B3065412C0@eu1rdcrdc1wx032.exi.nxp.com>
 <4F58F336.6090200@sil.org>
 <927C66C0775CCA43B88EB1E3006614B306541ABD@eu1rdcrdc1wx032.exi.nxp.com>
 <4F59200F.4090804@sil.org>
In-Reply-To: <4F59200F.4090804@sil.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Lars,

That is fair to say indeed.  In this case the cocoon instance you are refer=
ring to is the cocoon-servlet which is the main engine for any cocoon webap=
p.

I am not entirely sure though if the applications you refer to can be consi=
dered similar to the cocoon-blocks.  Although you mount them in a Uber site=
map, I don't think you can invoke services from 1 to another sitemap in 2.1=
.x versions of Cocoon although that could be best answered by the elder Coc=
oonistas ;-)

Have you ever heard of a WAR overlay?  You could also compare a cocoon app =
in some sense to this principle where the final WAR (webapp) is the result =
of merging all dependencies (cocoon-blocks).  But it's not really the same =
though.

A cocoon block typically (but optionally) consists of
 - resources (css / js / ...)
 - Java components
 - Spring application context (where you configure your beans)

It's like LEGO. You build isolated blocks (modules) of functionality but bl=
ocks can reuse each other (by declaring dependencies on each other).

In the final webapp project you include the blocks you need and you package=
 it all together into a war.=20

That's the global idea.

Robby

-----Original Message-----
From: Lars Huttar [mailto:lars_huttar@sil.org]=20
Sent: Thursday, March 08, 2012 10:10 PM
To: users@cocoon.apache.org
Cc: Robby Pelssers
Subject: Re: parent of parent artifact?

Thanks, that's very helpful!

We have a lot of  what we call "applications" that run side-by-side=20
under a single Cocoon 2 instance. They each live under a separate=20
subfolder (child of "mount/") under the main Cocoon sitemap. Each=20
"application" has its own sitemap.
It sounds like these "applications" actually correspond to the "blocks"=20
you describe below.

Is it fair to say that a Cocoon "web app" corresponds to one instance of=20
Cocoon running? So a "web app" can consist of several blocks?

Lars


On 3/8/2012 12:22 PM, Robby Pelssers wrote:
> Hey Lars,
>
> Great you ask these questions actually and I will try to answer to my bes=
t knowledge.
>
> * First of all your understanding of maven archetypes is completely corre=
ct.  A maven archetype is a project that creates a folder structure on your=
 file system where the archetype itself contains some default resources lik=
e e.g. a partially prefilled pom.xml and so on.
>
> * There is no need to declare any dependency on a cocoon block actually. =
But since version 2.2 Cocoon uses the servlet service framework.  I would c=
ompare a cocoon-block to a sub-webapp potentially providing some Java compo=
nents and pipelines which can be invoked from another cocoon-block.
>
> To give a concrete example.  At my customer I created 1 cocoon-block call=
ed 'shared' which provides services to fetch files from a XMLDB, Alfresco, =
file system.  As customer requirements grew, I created other blocks deliver=
ing needed functionality but they all need and use above described services=
. So in that case I only needed to declare a dependency on this 'shared' bl=
ock.
>
> That enables me to call this service from another sitemap as e.g.<map:gen=
erate src=3D"servlet:shared:/alfresco/{1}"/>  where {1} is some file identi=
fier.
>
> * Project / module / archetype and artifact are typical maven terms.
> - Project should need no explanation
> - module can be described as a part of the project
> - archetype is explained above
> - artifact is the thing that gets build when you run mvn package  (a war,=
 jar, ...)
>
> As a end user you should not be creating archetypes, merely using them as=
 shown in the previous mails. It will generate some skeleton maven projects=
 for you.
>
> Any further questions?
> Robby
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org