Return-Path: X-Original-To: apmail-cocoon-users-archive@www.apache.org Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 496FB9AF8 for ; Fri, 2 Mar 2012 16:02:46 +0000 (UTC) Received: (qmail 10475 invoked by uid 500); 2 Mar 2012 16:02:45 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 10422 invoked by uid 500); 2 Mar 2012 16:02:45 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 10414 invoked by uid 99); 2 Mar 2012 16:02:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2012 16:02:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [195.130.137.68] (HELO georges.telenet-ops.be) (195.130.137.68) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Mar 2012 16:02:36 +0000 Received: from [192.168.1.2] ([84.196.137.169]) by georges.telenet-ops.be with bizsmtp id gg2F1i00j3fUR3G06g2FfX; Fri, 02 Mar 2012 17:02:16 +0100 Message-ID: <4F50EF08.7020000@pandora.be> Date: Fri, 02 Mar 2012 17:02:16 +0100 From: Jos Snellings User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19 MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: How/where to create a sitemap in a generated Cocoon 3 web app? References: <4F4FFF4F.4090704@sil.org> <4F506D07.2050809@pandora.be> <4F50E7A4.2030401@sil.org> In-Reply-To: <4F50E7A4.2030401@sil.org> Content-Type: multipart/alternative; boundary="------------070206050208090303080309" X-Virus-Checked: Checked by ClamAV on apache.org --------------070206050208090303080309 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Well, that's two of us. In fact, three, as Francesco would be willing to contribute as well. The mail is a good starting point. And then I notice a **strong** suggestion to release. Put that together and we can get this thing rolling again! Let's rock! Have a nice weekend, Jos On 03/02/2012 04:30 PM, Lars Huttar wrote: > Jos, thanks for these helpful instructions! > > I will create a sitemap at src/main/resources/COB-INF/sitemap.xmap and > see how far that gets me. > > I agree, it would be very helpful to have a tutorial for newbies! I'll > be happy to make a contribution. > > Lars > > > On 3/2/2012 12:47 AM, Jos Snellings wrote: >> Hi Lars, >> >> The instructions on the site are obscure because they presuppose a >> good deal of Maven knowledge. >> Maven helps you to build the project: it puts all the files you need >> together and at first it feels metaphysical >> (hey, will you let me control my own build?). >> >> But here's what I do: >> >> ThingToKnow1: the elements you want to expose, and your sitemap are >> in the "block". Your "cocoon webapp" >> is going to "mount" (my word choice) the blocks on a virtual path. >> ThingToKnow2: You control Mavens behaviour through editing pom.xml. >> Add your Cocoon block as dependency means that you are going to edit >> the pom.xml. >> >> 1. create the webapp from the archetype. The webapp contains close >> to nothing. >> It will contain close to nothing. It should contain the >> "canonical structure" of a web project: >> pom.xml >> main >> main/resources >> main/webapp >> main/webapp/WEB-INF >> main/webapp/WEB-INF/applicationContext.xml >> main/webapp/WEB-INF/log4j.xml >> main/webapp/WEB-INF/web.xml >> >> Edit pom.xml, you will see the section "dependencies". Add the >> dependency for the block you want to add (I said "mount", >> but I guess that is old fashioned). >> >> >> >> org.tiaterra >> myCocoonBlock >> 1.0.0-SNAPSHOT >> >> >> >> 2. create your block from the archetype >> >> This will create a structure like: >> src >> src/test >> src/test/resources >> src/test/java >> src/main >> src/main/resources >> src/main/resources/COB-INF >> src/main/resources/COB-INF/javascript >> src/main/resources/COB-INF/xslt >> src/main/resources/COB-INF/images >> src/main/resources/COB-INF/style >> src/main/resources/COB-INF/style/images >> src/main/resources/COB-INF/static-content >> src/main/resources/META-INF >> src/main/resources/META-INF/cocoon >> src/main/resources/META-INF/cocoon/spring >> src/main/java >> src/main/java/org >> src/main/java/org/tanteterra >> >> Your site map is at: >> >> src/main/resources/COB-INF/sitemap.xmap >> >> And true, the documentation on the site does not make it easy enough >> to step >> up the threshold and upgrade. >> [@group: shouldn't we do something about that. Cocoon is losing its >> user base, >> it will end up getting adopted only by a few old people out there. It >> is gaining momentum on the planet Zork but that's not >> going to help us on Earth, is it?] >> >> I hope this helps you on the way. It would make me very happy to know >> that I am not one of the sole developers >> on this planet who chose cocoon 3 as a development platform, for the >> few times in your life that you are in the >> position to make this choice for your customer! I chose for cocoon 3 >> because I liked the new architecture. >> [@group: this can be the start for a tutorial for newbies, someone >> interested? I feel that the maven integration and >> the spring part deserve better explanation, they are way too arcane >> for starters. A tutorial could explain how to get things >> done without first studying two other frameworks.] >> >> Kind regards, >> Jos Snellings > --------------070206050208090303080309 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Well, that's two of us. In fact, three, as Francesco would be willing to contribute as well.
The mail is a good starting point. And then I notice a **strong** suggestion to release. Put that together
and we can get this thing rolling again!
Let's rock!

Have a nice weekend,
Jos

On 03/02/2012 04:30 PM, Lars Huttar wrote:
Jos, thanks for these helpful instructions!

I will create a sitemap at src/main/resources/COB-INF/sitemap.xmap and see how far that gets me.

I agree, it would be very helpful to have a tutorial for newbies! I'll be happy to make a contribution.

Lars


On 3/2/2012 12:47 AM, Jos Snellings wrote:
Hi Lars,

The instructions on the site are obscure because they presuppose a good deal of Maven knowledge.
Maven helps you to build the project: it puts all the files you need together and at first it feels metaphysical
(hey, will you let me control my own build?).

But here's what I do:

ThingToKnow1:  the elements you want to expose, and your sitemap are in the "block". Your "cocoon webapp"
is going to "mount" (my word choice) the blocks on a virtual path.
ThingToKnow2:  You control Mavens behaviour through editing pom.xml. Add your Cocoon block as dependency means that you are going to edit the pom.xml.

1.   create the webapp from the archetype. The webapp contains close to nothing.
      It will contain close to nothing. It should contain the "canonical structure" of a web project:
          pom.xml
          main
          main/resources
          main/webapp
          main/webapp/WEB-INF
          main/webapp/WEB-INF/applicationContext.xml
          main/webapp/WEB-INF/log4j.xml
          main/webapp/WEB-INF/web.xml 

Edit pom.xml, you will see the section "dependencies". Add the dependency for the block you want to add (I said "mount",
but I guess that is old fashioned).

<dependencies>
     <dependency>
      <groupId>org.tiaterra</groupId>
      <artifactId>myCocoonBlock</artifactId>
      <version>1.0.0-SNAPSHOT</version>
    </dependency>
  </dependencies>

2.  create your block from the archetype
     
     This will create a structure like: 
src
src/test
src/test/resources
src/test/java
src/main
src/main/resources
src/main/resources/COB-INF
src/main/resources/COB-INF/javascript
src/main/resources/COB-INF/xslt
src/main/resources/COB-INF/images
src/main/resources/COB-INF/style
src/main/resources/COB-INF/style/images
src/main/resources/COB-INF/static-content
src/main/resources/META-INF
src/main/resources/META-INF/cocoon
src/main/resources/META-INF/cocoon/spring
src/main/java
src/main/java/org
src/main/java/org/tanteterra

Your site map is at:
 
src/main/resources/COB-INF/sitemap.xmap

And true, the documentation on the site does not make it easy enough to step
up the threshold and upgrade.
[@group: shouldn't we do something about that. Cocoon is losing its user base,
it will end up getting adopted only by a few old people out there. It is gaining momentum on the planet Zork but that's not
going to help us on Earth, is it?]

I hope this helps you on the way. It would make me very happy to know that I am not one of the sole developers
on this planet who chose cocoon 3 as a development platform, for the few times in your life that you are in the
position to make this choice for your customer! I chose for cocoon 3 because I liked the new architecture.
[@group: this can be the start for a tutorial for newbies, someone interested? I feel that the maven integration and
the spring part deserve better explanation, they are way too arcane for starters. A tutorial could explain how to get things
done without first studying two other frameworks.]

Kind regards,
Jos Snellings


--------------070206050208090303080309--