cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agssa.net>
Subject Re: adding personal blocks to Cocoon build (was: 2.1.6 build fails looking for TraXLiaison)
Date Thu, 09 Dec 2004 02:42:20 GMT
Hi Bruce,

can you wikify it? ;-)

Best Regards,

Antonio Gallardo

On Mie, 8 de Diciembre de 2004, 16:41, Bruce Robertson dijo:
> Quoting Joerg Heinicke <joerg.heinicke@gmx.de>:
>
>> On 08.12.2004 23:01, Greg Newton wrote:
>>
>> > I want to incorporate the eXist xml database (http://exist-db.org/)
>> into
>> > my builds of Cocoon and I'd like to do it as a block (unless there are
>>
>> > compelling reasons to do it another way).
>> >
>> > Are there good (read no assumptions made about my competence level)
>> > online instructions for doing this, or is this something that really
>>
>> > requires alot of experience to do?
>> >
>> > There is a fellow that does this very thing (eXist as block) but I'd
>>
>> > like to learn *how* to do it rather than relying on others to do it
>> for me.
>>
>> There is not much meaning about a Cocoon *block* at the moment as it is
>>
>> more or less only a directory structure. Having the dirs and files at
>> the correct place lets them get incorporated into a Cocoon build.
>>
>> If you need some additional configuration in Cocoon files like
>> cocoon.xconf you have to write some xpatch files which get merged with
>>
>> the main cocoon.xconf (and maybe others).
>>
>> A third issue is the gump descriptor. I think you need an entry there to
>>
>> get your block added to the list of to-be-build blocks, but I do not
>> really know.
>>
>> I would really wonder if there are any online instructions about doing
>>
>> this. So learning by doing/copying & pasting from the existent blocks
>> will be the way to go. The most important parts I hopefully mentioned
>> above.
>>
>> Joerg
>
>
> One additional step is not mentioned in Joerg's description. You must get
> cocoon to build its xpatch task code before you can run it over this and
> that. A sample from the heml build.xml file is:
>
> <!-- XPatch Stuff  -->
> <target name="xpatch" depends="xpatch_gump,xpatch_jars"/>
>
>
> <target name="xpatch_init">
>   <ant antfile="${cocoon.home}/tools/targets/init-build.xml"
> dir="${cocoon.home}" target="init-tasks"/>
>
>
> <taskdef name="xpatch" classname="XConfToolTask"
> classpath="${cocoon.ant.tasks}"/>
> </target>
>
>
> <target name="xpatch_gump" depends="xpatch_init">
> <xpatch file="${cocoon.home}/gump.xml"
>      includes="xpatches/*.xgump"
> />
> </target>
>
>
> <target name="xpatch_jars" depends="xpatch_init">
> <xpatch file="${cocoon.home}/lib/jars.xml"
>         includes="xpatches/*.xjars"
> />
> </target>
>
>
> If someone is interested in doing this with their own project, they would
> probably find the exist_as_block code above the easiest to pick apart.
>
> Yrs,
> --
> Bruce Robertson,
> Dept. of Classics, Mount Allison University
> http://heml.mta.ca
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>


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


Mime
View raw message