You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Reinhard Poetz <re...@apache.org> on 2007/05/06 19:56:39 UTC
[docs] Reworking the "Getting started" section
I've started to split up our tutorials into smaller pieces in order to make them
more comprehensible:
* Your first Cocoon application using Maven 2
* Your first XML pipeline (publishing)
* Modularize Cocoon apps (Using blocks)
* Deploying a Cocoon application
Additionally we should have one or two tutorials that introduce into control
flow and cforms.
This should help new users to get up to speed very quickly. I haven't finished
them yet, but would be very interested in some feedback (too short/too long,
didactics, logical gaps, ...).
See
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1290.html
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1291.html
http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1362.html
Since I won't have time to write the flowscript/cforms tutorial, it would be
great if somebody else could help out. Thanks.
- o -
I also want to extend the block archetype so that it also contains a simple
publishing pipeline and a forms app. This adds a lot of things that are only
useful for beginners but not for somebody who is already familiar with Cocoon
blocks and only wants to create just another block. For them I will create an
archetype that is nearly empty.
WDYT?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Re: [docs] Reworking the "Getting started" section
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Reinhard Poetz pisze:
>
> I've started to split up our tutorials into smaller pieces in order to
> make them more comprehensible:
>
> * Your first Cocoon application using Maven 2
> * Your first XML pipeline (publishing)
> * Modularize Cocoon apps (Using blocks)
> * Deploying a Cocoon application
>
> Additionally we should have one or two tutorials that introduce into
> control flow and cforms.
>
> This should help new users to get up to speed very quickly. I haven't
> finished them yet, but would be very interested in some feedback (too
> short/too long, didactics, logical gaps, ...).
>
> See
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1290.html
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1291.html
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1362.html
Reinhard, you are making some much great effort that it's sometimes hard to follow docs list. ;-)
I've read them quite carefully and I think they look good. I will try to follow all instructions and build a block to see if there is no
typos and everything is really clear. Expect more useful comments soon.
> Since I won't have time to write the flowscript/cforms tutorial, it
> would be great if somebody else could help out. Thanks.
I was already thinking about it but I do not have that much free time to make it really well. If no one else offers his help I will try to
produce some useful pieces, though.
> - o -
>
> I also want to extend the block archetype so that it also contains a
> simple publishing pipeline and a forms app. This adds a lot of things
> that are only useful for beginners but not for somebody who is already
> familiar with Cocoon blocks and only wants to create just another block.
> For them I will create an archetype that is nearly empty.
+1
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: [OT] Lots of nested quotes
Posted by Grzegorz Kossakowski <gk...@apache.org>.
hepabolu napisał(a):
> Grzegorz Kossakowski said the following on 9/5/07 22:09:
>>
>> I hope you will like it. :-)
>
> And for those not fluent in Polish:
> https://addons.mozilla.org/en-US/thunderbird/addon/612
>
> :-)
Oups, I thought that language is not encoded in URL and bases on browser settings.
I think that is an apparent limitation of Mozilla site... :)
Thanks Helma! :-)
--
Grzegorz Kossakowski
Re: [OT] Lots of nested quotes
Posted by hepabolu <he...@gmail.com>.
Grzegorz Kossakowski said the following on 9/5/07 22:09:
> Take a look at the snippet above, it's long trail of useless information
> - noise. I know that you are as lazy as I'm but there is solution for
> Thunderbird users:
> https://addons.mozilla.org/pl/thunderbird/addon/612
>
> I hope you will like it. :-)
And for those not fluent in Polish:
https://addons.mozilla.org/en-US/thunderbird/addon/612
:-)
Bye, Helma
[OT] Lots of nested quotes (was: Re: [docs] Reworking the "Getting
started" section)
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Reinhard Poetz pisze:
> Marc Portier wrote:
>>
>>
>> Reinhard Poetz wrote:
>>> Marc Portier wrote:
>>>>
>>>>
>>>> Reinhard Poetz wrote:
>>>>> Marc Portier wrote:
>>>>>>
>>>>>> Reinhard Poetz wrote:
>>>>>>> I've started to split up our tutorials into smaller pieces in
>>>>>>> order to
>>>>>>> make them more comprehensible:
>>>>>>>
>>>>>>> * Your first Cocoon application using Maven 2
>>>>>>> * Your first XML pipeline (publishing)
>>>>>>> * Modularize Cocoon apps (Using blocks)
>>>>>>> * Deploying a Cocoon application
>>>>>>>
>>>>>>> Additionally we should have one or two tutorials that introduce into
>>>>>>> control flow and cforms.
>>>>>>>
>>>>>>> This should help new users to get up to speed very quickly. I
>>>>>>> haven't
>>>>>>> finished them yet, but would be very interested in some feedback
>>>>>>> (too
>>>>>>> short/too long, didactics, logical gaps, ...).
>>>>>>>
>>>>>>> See
>>>>>>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>>>>>>
>>>>>> this seems to have some glitches
>>>>>> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>>>>>>
>>>>>> * the block is named 'myBlock1', and thus the block-url should be
>>>>>> http://localhost:8888/myBlock1/
>>>>>>
>>>>>> (although we could also mention that this is due to the @mount-path
>>>>>> attribute in the
>>>>>> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
>>>>>
>>>>> ok
>>>>>
>>>>>> by the way:
>>>>>> * could somebody grant me (registered as mpo) some rights on the
>>>>>> daisy
>>>>>> instance so I can edit things like this myself? thx.
>>>>>
>>>>> done
>>>>>
>>>>
>>>> ok thx,
>>>> doing that now, and while working on this I realized why I had to
>>>> add the manual mvn cocoon:rcl in my case:
>>>>
>>>> unlike what is mentioned in the NOTE the cocoon-plugin's rcl goal
>>>> was NOT bound to the compile phase'
>>>
>>> yes, therefore the warning message on the top of
>>> http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html.
>>> Sorry for not mentioning it in my mail.
>>>
Take a look at the snippet above, it's long trail of useless information - noise. I know that you are as lazy as I'm but there is solution
for Thunderbird users:
https://addons.mozilla.org/pl/thunderbird/addon/612
I hope you will like it. :-)
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: [docs] Reworking the "Getting started" section
Posted by Reinhard Poetz <re...@apache.org>.
Marc Portier wrote:
>
>
> Reinhard Poetz wrote:
>> Marc Portier wrote:
>>>
>>>
>>> Reinhard Poetz wrote:
>>>> Marc Portier wrote:
>>>>>
>>>>> Reinhard Poetz wrote:
>>>>>> I've started to split up our tutorials into smaller pieces in
>>>>>> order to
>>>>>> make them more comprehensible:
>>>>>>
>>>>>> * Your first Cocoon application using Maven 2
>>>>>> * Your first XML pipeline (publishing)
>>>>>> * Modularize Cocoon apps (Using blocks)
>>>>>> * Deploying a Cocoon application
>>>>>>
>>>>>> Additionally we should have one or two tutorials that introduce into
>>>>>> control flow and cforms.
>>>>>>
>>>>>> This should help new users to get up to speed very quickly. I haven't
>>>>>> finished them yet, but would be very interested in some feedback (too
>>>>>> short/too long, didactics, logical gaps, ...).
>>>>>>
>>>>>> See
>>>>>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>>>>>
>>>>> this seems to have some glitches
>>>>> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>>>>>
>>>>> * the block is named 'myBlock1', and thus the block-url should be
>>>>> http://localhost:8888/myBlock1/
>>>>>
>>>>> (although we could also mention that this is due to the @mount-path
>>>>> attribute in the
>>>>> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
>>>>
>>>> ok
>>>>
>>>>> by the way:
>>>>> * could somebody grant me (registered as mpo) some rights on the daisy
>>>>> instance so I can edit things like this myself? thx.
>>>>
>>>> done
>>>>
>>>
>>> ok thx,
>>> doing that now, and while working on this I realized why I had to add
>>> the manual mvn cocoon:rcl in my case:
>>>
>>> unlike what is mentioned in the NOTE the cocoon-plugin's rcl goal was
>>> NOT bound to the compile phase'
>>
>> yes, therefore the warning message on the top of
>> http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html.
>> Sorry for not mentioning it in my mail.
>>
>
> I'ld say: sorry for not seeing that obvious remark :-P
>
>>> I used the archetype build from svn-trunk myself, the resulting pom
>>> had to be edited:
>>>
>>> <plugin>
>>> <groupId>org.apache.cocoon</groupId>
>>> <artifactId>cocoon-maven-plugin</artifactId>
>>> <version>1.0.0-M1-SNAPSHOT</version>
>>>
>>> <!-- this I had to add myself:
>>> <executions>
>>> <execution>
>>> <id>rcl</id>
>>> <phase>compile</phase>
>>> <goals>
>>> <goal>rcl</goal>
>>> </goals>
>>> </execution>
>>> </executions>
>>> -->
>>> </plugin>
>>>
>>> with that in place the mvn jetty:run will force the compile, and that
>>> will trigger the rcl
>>>
>>> if my understanding is correct, and you want me to, then I can update
>>> the archetype for you
>>
>> go ahead, thanks!
>>
>
> happy to
>
> see revision 536619.
>
> (http://svn.apache.org/viewvc?view=rev&revision=536619)
thanks
> as you can see I kept the <!-- comment-out of the plugin in place since
> probably not everybody would necessarily want to use the rcl plugin, right?
Not to use it means that you have to call "mvn install" on the block module and
on a webapp module that has a dependency on it. Then you also have to restart
your servlet container.
> in this case I think in the end some smart 'profile' would be better in
> providing the flexibility between those who want it and those who don't,
> for now just fiddling with <!-- is good enough IMHO
a profile is a good idea IMO
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [docs] Reworking the "Getting started" section
Posted by Marc Portier <mp...@outerthought.org>.
Reinhard Poetz wrote:
> Marc Portier wrote:
>>
>>
>> Reinhard Poetz wrote:
>>> Marc Portier wrote:
>>>>
>>>> Reinhard Poetz wrote:
>>>>> I've started to split up our tutorials into smaller pieces in order to
>>>>> make them more comprehensible:
>>>>>
>>>>> * Your first Cocoon application using Maven 2
>>>>> * Your first XML pipeline (publishing)
>>>>> * Modularize Cocoon apps (Using blocks)
>>>>> * Deploying a Cocoon application
>>>>>
>>>>> Additionally we should have one or two tutorials that introduce into
>>>>> control flow and cforms.
>>>>>
>>>>> This should help new users to get up to speed very quickly. I haven't
>>>>> finished them yet, but would be very interested in some feedback (too
>>>>> short/too long, didactics, logical gaps, ...).
>>>>>
>>>>> See
>>>>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>>>>
>>>> this seems to have some glitches
>>>> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>>>>
>>>> * the block is named 'myBlock1', and thus the block-url should be
>>>> http://localhost:8888/myBlock1/
>>>>
>>>> (although we could also mention that this is due to the @mount-path
>>>> attribute in the
>>>> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
>>>
>>> ok
>>>
>>>> by the way:
>>>> * could somebody grant me (registered as mpo) some rights on the daisy
>>>> instance so I can edit things like this myself? thx.
>>>
>>> done
>>>
>>
>> ok thx,
>> doing that now, and while working on this I realized why I had to add
>> the manual mvn cocoon:rcl in my case:
>>
>> unlike what is mentioned in the NOTE the cocoon-plugin's rcl goal was
>> NOT bound to the compile phase'
>
> yes, therefore the warning message on the top of
> http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html. Sorry
> for not mentioning it in my mail.
>
I'ld say: sorry for not seeing that obvious remark :-P
>> I used the archetype build from svn-trunk myself, the resulting pom
>> had to be edited:
>>
>> <plugin>
>> <groupId>org.apache.cocoon</groupId>
>> <artifactId>cocoon-maven-plugin</artifactId>
>> <version>1.0.0-M1-SNAPSHOT</version>
>>
>> <!-- this I had to add myself:
>> <executions>
>> <execution>
>> <id>rcl</id>
>> <phase>compile</phase>
>> <goals>
>> <goal>rcl</goal>
>> </goals>
>> </execution>
>> </executions>
>> -->
>> </plugin>
>>
>> with that in place the mvn jetty:run will force the compile, and that
>> will trigger the rcl
>>
>> if my understanding is correct, and you want me to, then I can update
>> the archetype for you
>
> go ahead, thanks!
>
happy to
see revision 536619.
(http://svn.apache.org/viewvc?view=rev&revision=536619)
as you can see I kept the <!-- comment-out of the plugin in place since
probably not everybody would necessarily want to use the rcl plugin, right?
in this case I think in the end some smart 'profile' would be better in
providing the flexibility between those who want it and those who don't,
for now just fiddling with <!-- is good enough IMHO
regards,
-marc=
Re: [docs] Reworking the "Getting started" section
Posted by Reinhard Poetz <re...@apache.org>.
Marc Portier wrote:
>
>
> Reinhard Poetz wrote:
>> Marc Portier wrote:
>>>
>>> Reinhard Poetz wrote:
>>>> I've started to split up our tutorials into smaller pieces in order to
>>>> make them more comprehensible:
>>>>
>>>> * Your first Cocoon application using Maven 2
>>>> * Your first XML pipeline (publishing)
>>>> * Modularize Cocoon apps (Using blocks)
>>>> * Deploying a Cocoon application
>>>>
>>>> Additionally we should have one or two tutorials that introduce into
>>>> control flow and cforms.
>>>>
>>>> This should help new users to get up to speed very quickly. I haven't
>>>> finished them yet, but would be very interested in some feedback (too
>>>> short/too long, didactics, logical gaps, ...).
>>>>
>>>> See
>>>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>>>
>>> this seems to have some glitches
>>> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>>>
>>> * the block is named 'myBlock1', and thus the block-url should be
>>> http://localhost:8888/myBlock1/
>>>
>>> (although we could also mention that this is due to the @mount-path
>>> attribute in the
>>> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
>>
>> ok
>>
>>> by the way:
>>> * could somebody grant me (registered as mpo) some rights on the daisy
>>> instance so I can edit things like this myself? thx.
>>
>> done
>>
>
> ok thx,
> doing that now, and while working on this I realized why I had to add
> the manual mvn cocoon:rcl in my case:
>
> unlike what is mentioned in the NOTE the cocoon-plugin's rcl goal was
> NOT bound to the compile phase'
yes, therefore the warning message on the top of
http://cocoon.zones.apache.org/daisy/cdocs-site-main/g2/1159.html. Sorry for not
mentioning it in my mail.
> I used the archetype build from svn-trunk myself, the resulting pom had
> to be edited:
>
> <plugin>
> <groupId>org.apache.cocoon</groupId>
> <artifactId>cocoon-maven-plugin</artifactId>
> <version>1.0.0-M1-SNAPSHOT</version>
>
> <!-- this I had to add myself:
> <executions>
> <execution>
> <id>rcl</id>
> <phase>compile</phase>
> <goals>
> <goal>rcl</goal>
> </goals>
> </execution>
> </executions>
> -->
> </plugin>
>
> with that in place the mvn jetty:run will force the compile, and that
> will trigger the rcl
>
> if my understanding is correct, and you want me to, then I can update
> the archetype for you
go ahead, thanks!
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [docs] Reworking the "Getting started" section
Posted by Marc Portier <mp...@outerthought.org>.
Reinhard Poetz wrote:
> Marc Portier wrote:
>>
>> Reinhard Poetz wrote:
>>> I've started to split up our tutorials into smaller pieces in order to
>>> make them more comprehensible:
>>>
>>> * Your first Cocoon application using Maven 2
>>> * Your first XML pipeline (publishing)
>>> * Modularize Cocoon apps (Using blocks)
>>> * Deploying a Cocoon application
>>>
>>> Additionally we should have one or two tutorials that introduce into
>>> control flow and cforms.
>>>
>>> This should help new users to get up to speed very quickly. I haven't
>>> finished them yet, but would be very interested in some feedback (too
>>> short/too long, didactics, logical gaps, ...).
>>>
>>> See
>>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>>
>> this seems to have some glitches
>> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>>
>> * the block is named 'myBlock1', and thus the block-url should be
>> http://localhost:8888/myBlock1/
>>
>> (although we could also mention that this is due to the @mount-path
>> attribute in the
>> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
>
> ok
>
>> by the way:
>> * could somebody grant me (registered as mpo) some rights on the daisy
>> instance so I can edit things like this myself? thx.
>
> done
>
ok thx,
doing that now, and while working on this I realized why I had to add
the manual mvn cocoon:rcl in my case:
unlike what is mentioned in the NOTE the cocoon-plugin's rcl goal was
NOT bound to the compile phase'
I used the archetype build from svn-trunk myself, the resulting pom had
to be edited:
<plugin>
<groupId>org.apache.cocoon</groupId>
<artifactId>cocoon-maven-plugin</artifactId>
<version>1.0.0-M1-SNAPSHOT</version>
<!-- this I had to add myself:
<executions>
<execution>
<id>rcl</id>
<phase>compile</phase>
<goals>
<goal>rcl</goal>
</goals>
</execution>
</executions>
-->
</plugin>
with that in place the mvn jetty:run will force the compile, and that
will trigger the rcl
if my understanding is correct, and you want me to, then I can update
the archetype for you
regards,
-marc=
Re: [docs] Reworking the "Getting started" section
Posted by Reinhard Poetz <re...@apache.org>.
Grzegorz Kossakowski wrote:
> Reinhard Poetz pisze:
>>> * I noticed the cocoon-maven-plugin is at 1.0.0-M1-SNAPSHOT while the
>>> rest of trunk seems to be talking about 1.0.0-RC1-SNAPSHOT, any
>>> compelling reason?
>>
>> I want to see more user feedback before we release a RC because doing
>> all those classloader tricks has been difficult and I expect more
>> problems showing up.
>
> I think that we should have M1 release of cocoon-maven-plugin before (or
> at the same time) rest of artifacts are released as RC1. This will
> result in much wider audience and better testing.
>
> WDYT?
yes, that's my plan. BTW, there is another reason for a milestone release: The
plugin depends on commons-jci-1.0-RC1 which isn't available at the central Maven
repo.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [docs] Reworking the "Getting started" section
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Reinhard Poetz pisze:
>> * I noticed the cocoon-maven-plugin is at 1.0.0-M1-SNAPSHOT while the
>> rest of trunk seems to be talking about 1.0.0-RC1-SNAPSHOT, any
>> compelling reason?
>
> I want to see more user feedback before we release a RC because doing
> all those classloader tricks has been difficult and I expect more
> problems showing up.
I think that we should have M1 release of cocoon-maven-plugin before (or at the same time) rest of artifacts are released as RC1. This will
result in much wider audience and better testing.
WDYT?
--
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/
Re: [docs] Reworking the "Getting started" section
Posted by Reinhard Poetz <re...@apache.org>.
Marc Portier wrote:
>
> Reinhard Poetz wrote:
>> I've started to split up our tutorials into smaller pieces in order to
>> make them more comprehensible:
>>
>> * Your first Cocoon application using Maven 2
>> * Your first XML pipeline (publishing)
>> * Modularize Cocoon apps (Using blocks)
>> * Deploying a Cocoon application
>>
>> Additionally we should have one or two tutorials that introduce into
>> control flow and cforms.
>>
>> This should help new users to get up to speed very quickly. I haven't
>> finished them yet, but would be very interested in some feedback (too
>> short/too long, didactics, logical gaps, ...).
>>
>> See
>> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
>
> this seems to have some glitches
> * I had to mvn cococoon:rcl in order for mvn jetty:run to work
>
> * the block is named 'myBlock1', and thus the block-url should be
> http://localhost:8888/myBlock1/
>
> (although we could also mention that this is due to the @mount-path
> attribute in the
> src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
ok
> by the way:
> * could somebody grant me (registered as mpo) some rights on the daisy
> instance so I can edit things like this myself? thx.
done
> * I noticed the cocoon-maven-plugin is at 1.0.0-M1-SNAPSHOT while the
> rest of trunk seems to be talking about 1.0.0-RC1-SNAPSHOT, any
> compelling reason?
I want to see more user feedback before we release a RC because doing all those
classloader tricks has been difficult and I expect more problems showing up.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
Re: [docs] Reworking the "Getting started" section
Posted by Marc Portier <mp...@outerthought.org>.
Reinhard Poetz wrote:
>
> I've started to split up our tutorials into smaller pieces in order to
> make them more comprehensible:
>
> * Your first Cocoon application using Maven 2
> * Your first XML pipeline (publishing)
> * Modularize Cocoon apps (Using blocks)
> * Deploying a Cocoon application
>
> Additionally we should have one or two tutorials that introduce into
> control flow and cforms.
>
> This should help new users to get up to speed very quickly. I haven't
> finished them yet, but would be very interested in some feedback (too
> short/too long, didactics, logical gaps, ...).
>
> See
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1159.html
this seems to have some glitches
* I had to mvn cococoon:rcl in order for mvn jetty:run to work
* the block is named 'myBlock1', and thus the block-url should be
http://localhost:8888/myBlock1/
(although we could also mention that this is due to the @mount-path
attribute in the
src/main/resources/META-INF/cocoon/spring/servlet-service.xml)
by the way:
* could somebody grant me (registered as mpo) some rights on the daisy
instance so I can edit things like this myself? thx.
* I noticed the cocoon-maven-plugin is at 1.0.0-M1-SNAPSHOT while the
rest of trunk seems to be talking about 1.0.0-RC1-SNAPSHOT, any
compelling reason?
haven't checked the rest yet.
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1290.html
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1291.html
> http://cocoon.zones.apache.org/daisy/cdocs/g2/g1/g2/1362.html
>
> Since I won't have time to write the flowscript/cforms tutorial, it
> would be great if somebody else could help out. Thanks.
>
> - o -
>
> I also want to extend the block archetype so that it also contains a
> simple publishing pipeline and a forms app. This adds a lot of things
> that are only useful for beginners but not for somebody who is already
> familiar with Cocoon blocks and only wants to create just another block.
> For them I will create an archetype that is nearly empty.
>
> WDYT?
>
good initiative,
regards,
-marc= (trying to keep a closer eye on the cocoon-docs list)
Re: [docs] Reworking the "Getting started" section
Posted by Andrew Savory <an...@luminas.co.uk>.
Hi,
On 6 May 2007, at 18:56, Reinhard Poetz wrote:
> This should help new users to get up to speed very quickly. I
> haven't finished them yet, but would be very interested in some
> feedback (too short/too long, didactics, logical gaps, ...).
Will take a look and see what I can do.
> I also want to extend the block archetype so that it also contains
> a simple publishing pipeline and a forms app. This adds a lot of
> things that are only useful for beginners but not for somebody who
> is already familiar with Cocoon blocks and only wants to create
> just another block. For them I will create an archetype that is
> nearly empty.
Heh ... since last month I've had an email in my drafts folder saying
exactly this ;-)
I'd like to add:
content
stylesheets
error handlers
I actually have most of that written already (I was originally
planning to commit it before my apachecon talk, but ran out of time).
I can commit it if we agree what should be there.
Thanks,
Andrew.
--
Andrew Savory, Managing Director, Sourcesense UK
Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135
Web: http://www.sourcesense.com/