You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pier Fumagalli <pi...@betaversion.org> on 2005/09/05 02:49:03 UTC
Blocks in 2.2
Any special note on how to do blocks in 2.2?
I've created this week two new blocks "validation" and "captcha", and
I would love to see them in sync on HEAD (and not only in BRANCH_2_1_x).
With all this OSGI stuff and work, I lost track of HEAD. Anyone care
to explain like I was a three-years-old???
Pier
PS: I noticed that in the 2.1.x branch, most of the XMAPs in the
block samples declare elements within the "map" namespace for
patching, but don't declare the namespace itself. I suspect this is
because ANT doesn't use a namespace-aware parser (bytes me how), but
XMLLINT reports failures for a number of files (see list below). In
my blocks I declare the namespace and that doesn't seem to create any
problems, should we go ahead and fix the wrong ones?
src/blocks/asciiart/conf/asciiart-generator.xmap
src/blocks/authentication-fw/conf/authentication-act.xmap
src/blocks/authentication-fw/conf/authentication-gen.xmap
src/blocks/batik/conf/svg.generation.xmap
src/blocks/batik/conf/svg.serializer.xmap
src/blocks/batik/conf/svg.transformer.xmap
src/blocks/bsf/conf/bsf.xmap
src/blocks/chaperon/conf/chaperon-generator.xmap
src/blocks/chaperon/conf/chaperon-transformator.xmap
src/blocks/databases/conf/databases-trans.xmap
src/blocks/deli/conf/deli.xmap
src/blocks/fop/conf/fop.xmap
src/blocks/forms/conf/forms-generator.xmap
src/blocks/forms/conf/forms-transformator.xmap
src/blocks/html/conf/html-transformer.xmap
src/blocks/html/conf/html.xmap
src/blocks/itext/conf/itext.xmap
src/blocks/jfor/conf/jfor.xmap
src/blocks/jsp/conf/jsp.generator.xmap
src/blocks/jsp/conf/jsp.xmap
src/blocks/lucene/conf/lucene.xmap
src/blocks/midi/conf/midi.generator.xmap
src/blocks/midi/conf/midi.serializer.xmap
src/blocks/naming/conf/naming.xmap
src/blocks/php/conf/php.xmap
src/blocks/poi/conf/poi.xmap
src/blocks/portal-fw/conf/portal-act.xmap
src/blocks/portal-fw/conf/portal-gen.xmap
src/blocks/profiler/conf/profiler.component.xmap
src/blocks/profiler/conf/profiler.xmap
src/blocks/proxy/conf/proxy.xmap
src/blocks/proxy/conf/wsproxy.xmap
src/blocks/serializers/conf/serializers.serializer.xmap
src/blocks/session-fw/conf/session-act.xmap
src/blocks/session-fw/conf/session-sel.xmap
src/blocks/session-fw/conf/session-tran.xmap
src/blocks/slop/conf/slop-generator.xmap
src/blocks/stx/conf/stx-transformer.xmap
src/blocks/swf/conf/swf.xmap
src/blocks/velocity/conf/velocity.xmap
src/blocks/webdav/conf/webdav.xmap
src/blocks/xmldb/conf/xmldb.transformer.xmap
src/blocks/xsltal/conf/xsltal.xmap
src/blocks/xsp/conf/xsp-action.xmap
src/blocks/xsp/conf/xsp-generator.xmap
Re: Blocks in 2.2
Posted by Daniel Fagerstrom <da...@nada.kth.se>.
Pier Fumagalli wrote:
> Any special note on how to do blocks in 2.2?
Take a look at a couple of blocks in trunk and you will see how it is
done. No big changes since 2.1, main changes is about directory
structure and names, IIRC.
> I've created this week two new blocks "validation" and "captcha", and
> I would love to see them in sync on HEAD (and not only in BRANCH_2_1_x).
Please do.
> With all this OSGI stuff and work, I lost track of HEAD. Anyone care
> to explain like I was a three-years-old???
You don't need to care about OSGi for adding your block. The OSGi stuff
is still experimental and only tried partly at a few blocks. We will
also try to make everything including configuration files as back
compatible as possible.
If you want to join the OSGi work I can try to explain how it works.
/Daniel
Re: Fixing block XCONF files (Was: Re: Blocks in 2.2)
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 5 sept. 05, à 23:30, Pier Fumagalli a écrit :
> ...These are the errors I get from XML files in the blocks/conf:
>
> ojb/conf/repository_database.xml:74: parser error : Extra content at
> the end of the document
> <jdbc-connection-descriptor jcd-alias="personnel"
> default-connection="true">
> ...Those, though, are beyond my understanding in fixing...
Hmm..OJB uses entities to include XML document fragments into its
config, so I don't know if there's an easy fix.
-Bertrand
Fixing block XCONF files (Was: Re: Blocks in 2.2)
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 5 Sep 2005, at 17:41, Bertrand Delacretaz wrote:
> Le 5 sept. 05, à 02:49, Pier Fumagalli a écrit :
>
>> ...PS: I noticed that in the 2.1.x branch, most of the XMAPs in
>> the block samples declare elements within the "map" namespace for
>> patching, but don't declare the namespace itself. I suspect this
>> is because ANT doesn't use a namespace-aware parser (bytes me
>> how), but XMLLINT reports failures for a number of files (see list
>> below). In my blocks I declare the namespace and that doesn't seem
>> to create any problems, should we go ahead and fix the wrong ones?..
>
> Yes, one reason is to be able to use the refdoc block to generate
> documentation from them, by annotating them - they must be
> parseable for this to work.
Kewl, that's now done, there's only one thing puzzling me. These are
the errors I get from XML files in the blocks/conf:
ojb/conf/repository_database.xml:74: parser error : Extra content at
the end of the document
<jdbc-connection-descriptor jcd-alias="personnel" default-
connection="true">
^
ojb/conf/repository_internal.xml:62: parser error : Extra content at
the end of the document
<class-descriptor
^
ojb/conf/repository_user.xml:28: parser error : Extra content at the
end of the document
<class-descriptor
class="org.apache.cocoon.ojb.samples.bean.Employee" table=
^
Those, though, are beyond my understanding in fixing...
Pier
Re: Blocks in 2.2
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 5 sept. 05, à 02:49, Pier Fumagalli a écrit :
> ...PS: I noticed that in the 2.1.x branch, most of the XMAPs in the
> block samples declare elements within the "map" namespace for
> patching, but don't declare the namespace itself. I suspect this is
> because ANT doesn't use a namespace-aware parser (bytes me how), but
> XMLLINT reports failures for a number of files (see list below). In my
> blocks I declare the namespace and that doesn't seem to create any
> problems, should we go ahead and fix the wrong ones?..
Yes, one reason is to be able to use the refdoc block to generate
documentation from them, by annotating them - they must be parseable
for this to work.
-Bertrand
making sitemap fragments independently parseable [Re: Blocks in 2.2]
Posted by Stefano Mazzocchi <st...@apache.org>.
Pier Fumagalli wrote:
> PS: I noticed that in the 2.1.x branch, most of the XMAPs in the block
> samples declare elements within the "map" namespace for patching, but
> don't declare the namespace itself. I suspect this is because ANT
> doesn't use a namespace-aware parser (bytes me how), but XMLLINT
> reports failures for a number of files (see list below). In my blocks I
> declare the namespace and that doesn't seem to create any problems,
> should we go ahead and fix the wrong ones?
>
> src/blocks/asciiart/conf/asciiart-generator.xmap
> src/blocks/authentication-fw/conf/authentication-act.xmap
> src/blocks/authentication-fw/conf/authentication-gen.xmap
> src/blocks/batik/conf/svg.generation.xmap
> src/blocks/batik/conf/svg.serializer.xmap
> src/blocks/batik/conf/svg.transformer.xmap
> src/blocks/bsf/conf/bsf.xmap
> src/blocks/chaperon/conf/chaperon-generator.xmap
> src/blocks/chaperon/conf/chaperon-transformator.xmap
> src/blocks/databases/conf/databases-trans.xmap
> src/blocks/deli/conf/deli.xmap
> src/blocks/fop/conf/fop.xmap
> src/blocks/forms/conf/forms-generator.xmap
> src/blocks/forms/conf/forms-transformator.xmap
> src/blocks/html/conf/html-transformer.xmap
> src/blocks/html/conf/html.xmap
> src/blocks/itext/conf/itext.xmap
> src/blocks/jfor/conf/jfor.xmap
> src/blocks/jsp/conf/jsp.generator.xmap
> src/blocks/jsp/conf/jsp.xmap
> src/blocks/lucene/conf/lucene.xmap
> src/blocks/midi/conf/midi.generator.xmap
> src/blocks/midi/conf/midi.serializer.xmap
> src/blocks/naming/conf/naming.xmap
> src/blocks/php/conf/php.xmap
> src/blocks/poi/conf/poi.xmap
> src/blocks/portal-fw/conf/portal-act.xmap
> src/blocks/portal-fw/conf/portal-gen.xmap
> src/blocks/profiler/conf/profiler.component.xmap
> src/blocks/profiler/conf/profiler.xmap
> src/blocks/proxy/conf/proxy.xmap
> src/blocks/proxy/conf/wsproxy.xmap
> src/blocks/serializers/conf/serializers.serializer.xmap
> src/blocks/session-fw/conf/session-act.xmap
> src/blocks/session-fw/conf/session-sel.xmap
> src/blocks/session-fw/conf/session-tran.xmap
> src/blocks/slop/conf/slop-generator.xmap
> src/blocks/stx/conf/stx-transformer.xmap
> src/blocks/swf/conf/swf.xmap
> src/blocks/velocity/conf/velocity.xmap
> src/blocks/webdav/conf/webdav.xmap
> src/blocks/xmldb/conf/xmldb.transformer.xmap
> src/blocks/xsltal/conf/xsltal.xmap
> src/blocks/xsp/conf/xsp-action.xmap
> src/blocks/xsp/conf/xsp-generator.xmap
+1
--
Stefano.