You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Tak-po Li <ta...@gmail.com> on 2008/08/31 01:59:18 UTC
re: cforms
How should I install Cforms block into "getting-strat-app" environment?
Should I generate "myBlock3" and copy cocoon-cforms-impl-1.1.0.jar (unzipped
from the cform .zip file) into some directory and link all three blocks
together? I am new with cocoon. Could someone please help?
Thanks,
Tak
Re: cforms
Posted by Tak-po Li <ta...@gmail.com>.
Thanks, David, I am going to have a try.
Tak
On 8/31/08, David Legg <da...@searchevent.co.uk> wrote:
>
> Hi Tak,
>
> How should I install Cforms block into "getting-strat-app" environment?
>> Should I generate "myBlock3" and copy cocoon-cforms-impl-1.1.0.jar
>> (unzipped from the cform .zip file) into some directory and link all three
>> blocks together?
>>
>
> There is a tutorial on the Cocoon website showing how to add a Cocoon form
> under Cocoon 2.2 [1]. It may be a tiny bit out of date but it should tell
> you what you want to know.
>
> Just to recap; a Cocoon Block is nothing more than a jar file containing
> files in a certain expected directory structure. When you come to build a
> Cocoon application all you are doing is mixing the pre-built Cocoon Blocks
> that go with a certain release of Cocoon together with your own Cocoon
> blocks that get generated from your project's source and resource files.
>
> There is no need to create 'myBlock3' as that has effectively already been
> done for you... that is what the cocoon-forms-impl jar file is.
>
> All you have to do is tell Maven that your project depends on this jar by
> adding it to the dependency list in the pom.xml file and Maven will download
> it and install it into its own local repository ready to be added to the
> class path when you run your app.
>
> Hope that makes it clearer.
>
> Regards,
> David Legg
>
> [1] http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
Re: cforms
Posted by Tak-po Li <ta...@gmail.com>.
Thanks, Martin and Andre,
I reset my XP and rerun "mvn jetty:run". Same error happens, then I switch
to known block (myBlock1) that I built previously and run "mvn jetty:run".
MyBlock1 works.
It seems the problem is not in Jetty run time.
Thanks,
Tak
On 9/2/08, Andre Juffer <an...@oulu.fi> wrote:
>
> Tak-po Li wrote:
>
>> I followed the Cform instruction. All steps are OK until "mvn
>> jetty:run". I got Build Error "Address already in use: bind". Could any
>> one help?
>>
>
> This probably means that you already running a mvn process with goal
> jetty:run.
>
> How can I clear up files build by Maven to start a fresh new build?
>> Thanks,
>> Tak
>>
>>
>> On 8/31/08, *David Legg* <david.legg@searchevent.co.uk <mailto:
>> david.legg@searchevent.co.uk>> wrote:
>>
>> Hi Tak,
>>
>> How should I install Cforms block into "getting-strat-app"
>> environment? Should I generate "myBlock3" and copy
>> cocoon-cforms-impl-1.1.0.jar (unzipped from the cform .zip file)
>> into some directory and link all three blocks together?
>>
>>
>> There is a tutorial on the Cocoon website showing how to add a
>> Cocoon form under Cocoon 2.2 [1]. It may be a tiny bit out of date
>> but it should tell you what you want to know.
>>
>> Just to recap; a Cocoon Block is nothing more than a jar file
>> containing files in a certain expected directory structure. When
>> you come to build a Cocoon application all you are doing is mixing
>> the pre-built Cocoon Blocks that go with a certain release of Cocoon
>> together with your own Cocoon blocks that get generated from your
>> project's source and resource files.
>>
>> There is no need to create 'myBlock3' as that has effectively
>> already been done for you... that is what the cocoon-forms-impl jar
>> file is.
>>
>> All you have to do is tell Maven that your project depends on this
>> jar by adding it to the dependency list in the pom.xml file and
>> Maven will download it and install it into its own local repository
>> ready to be added to the class path when you run your app.
>>
>> Hope that makes it clearer.
>>
>> Regards,
>> David Legg
>>
>> [1] http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html
>> <http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> <ma...@cocoon.apache.org>
>> For additional commands, e-mail: users-help@cocoon.apache.org
>> <ma...@cocoon.apache.org>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
Re: cforms
Posted by Andre Juffer <an...@oulu.fi>.
Tak-po Li wrote:
>
> I followed the Cform instruction. All steps are OK until "mvn
> jetty:run". I got Build Error "Address already in use: bind". Could
> any one help?
This probably means that you already running a mvn process with goal
jetty:run.
>
> How can I clear up files build by Maven to start a fresh new build?
>
> Thanks,
>
> Tak
>
>
>
>
>
> On 8/31/08, *David Legg* <david.legg@searchevent.co.uk
> <ma...@searchevent.co.uk>> wrote:
>
> Hi Tak,
>
> How should I install Cforms block into "getting-strat-app"
> environment? Should I generate "myBlock3" and copy
> cocoon-cforms-impl-1.1.0.jar (unzipped from the cform .zip file)
> into some directory and link all three blocks together?
>
>
> There is a tutorial on the Cocoon website showing how to add a
> Cocoon form under Cocoon 2.2 [1]. It may be a tiny bit out of date
> but it should tell you what you want to know.
>
> Just to recap; a Cocoon Block is nothing more than a jar file
> containing files in a certain expected directory structure. When
> you come to build a Cocoon application all you are doing is mixing
> the pre-built Cocoon Blocks that go with a certain release of Cocoon
> together with your own Cocoon blocks that get generated from your
> project's source and resource files.
>
> There is no need to create 'myBlock3' as that has effectively
> already been done for you... that is what the cocoon-forms-impl jar
> file is.
>
> All you have to do is tell Maven that your project depends on this
> jar by adding it to the dependency list in the pom.xml file and
> Maven will download it and install it into its own local repository
> ready to be added to the class path when you run your app.
>
> Hope that makes it clearer.
>
> Regards,
> David Legg
>
> [1] http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html
> <http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> <ma...@cocoon.apache.org>
> For additional commands, e-mail: users-help@cocoon.apache.org
> <ma...@cocoon.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: cforms
Posted by Martin Heiden <ma...@netcologne.de>.
Hi!
Tak-po Li schrieb:
>
> I followed the Cform instruction. All steps are OK until "mvn
> jetty:run". I got Build Error "Address already in use: bind". Could
> any one help?
>
Stop the jetty instance which is listening on Port 8888 before you start
another ;-)
cheers
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: cforms
Posted by Tak-po Li <ta...@gmail.com>.
I followed the Cform instruction. All steps are OK until "mvn jetty:run".
I got Build Error "Address already in use: bind". Could any one help?
How can I clear up files build by Maven to start a fresh new build?
Thanks,
Tak
On 8/31/08, David Legg <da...@searchevent.co.uk> wrote:
>
> Hi Tak,
>
> How should I install Cforms block into "getting-strat-app" environment?
>> Should I generate "myBlock3" and copy cocoon-cforms-impl-1.1.0.jar
>> (unzipped from the cform .zip file) into some directory and link all three
>> blocks together?
>>
>
> There is a tutorial on the Cocoon website showing how to add a Cocoon form
> under Cocoon 2.2 [1]. It may be a tiny bit out of date but it should tell
> you what you want to know.
>
> Just to recap; a Cocoon Block is nothing more than a jar file containing
> files in a certain expected directory structure. When you come to build a
> Cocoon application all you are doing is mixing the pre-built Cocoon Blocks
> that go with a certain release of Cocoon together with your own Cocoonblocks that get generated from your project's source and resource files.
>
> There is no need to create 'myBlock3' as that has effectively already been
> done for you... that is what the cocoon-forms-impl jar file is.
>
> All you have to do is tell Maven that your project depends on this jar by
> adding it to the dependency list in the pom.xml file and Maven will download
> it and install it into its own local repository ready to be added to the
> class path when you run your app.
>
> Hope that makes it clearer.
>
> Regards,
> David Legg
>
> [1] http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>
Re: cforms
Posted by David Legg <da...@searchevent.co.uk>.
Hi Tak,
> How should I install Cforms block into "getting-strat-app"
> environment? Should I generate "myBlock3" and copy
> cocoon-cforms-impl-1.1.0.jar (unzipped from the cform .zip file) into
> some directory and link all three blocks together?
There is a tutorial on the Cocoon website showing how to add a Cocoon
form under Cocoon 2.2 [1]. It may be a tiny bit out of date but it
should tell you what you want to know.
Just to recap; a Cocoon Block is nothing more than a jar file containing
files in a certain expected directory structure. When you come to build
a Cocoon application all you are doing is mixing the pre-built Cocoon
Blocks that go with a certain release of Cocoon together with your own
Cocoon blocks that get generated from your project's source and resource
files.
There is no need to create 'myBlock3' as that has effectively already
been done for you... that is what the cocoon-forms-impl jar file is.
All you have to do is tell Maven that your project depends on this jar
by adding it to the dependency list in the pom.xml file and Maven will
download it and install it into its own local repository ready to be
added to the class path when you run your app.
Hope that makes it clearer.
Regards,
David Legg
[1] http://cocoon.apache.org/2.2/blocks/forms/1.0/478_1_1.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org