[docs] regenerated website; why extra docs?

[David Crossley]

Today i re-generated the cocoon.apache.org/2.1/ website
which incorporates a few changes to the Daisy sources,
fixes some links that used local hrefs, removes the
old ApacheCon logo.

There were some new documents generated which do not
have any mapping in the navigation. Does someone know
what should happen with them? ...

372.html
378.html
400.html
592.html
692.html
693.html
695.html
696.html
697.html
698.html
699.html
700.html
701.html
702.html
703.html
704.html
705.html
706.html
726.html
728.html
748.html
749.html

-David

Re: src/webapp/WEB-INF/entities

[David Crossley]

Jean-Baptiste Quenot wrote:
> 
> I would like to know what purpose serves the existing resources in
> webapp/WEB-INF/entities?  I know that one can setup a catalog for
> resolving entities, but I'm talking about all the stuff: DTDs,
> schemas, etc.  Is it really useful for a mean web application?

The configuration stuff is definitely necessary.

Many of the resources are probably not necessary.
For example, the document-v*.dtd etc. were needed when
we had the Cocoon documentation packaged with the webapp
and generated by Cocoon. That has all been ripped out
so probably don't need them.

> In the README, there is a message that I don't understand:
> 
> ??Please keep these resources in sync with the authoritative stuff
> at Forrest.??

The DTDs started life at Cocoon, then Forrest took over
the maintenance. With the documentation situation that
is mentioned above, we did need to keep these synchronised.

> I'm proposing to add a build option to avoid copying all these
> often-unnecessary resources.
> 
> WDYT?

Perhaps better to remove the stuff that we don't need.
I would suggest to leave the ISO*.pen entity sets
which are often needed by applications.

The entities/w3c/svg*.dtd might be needed, i don't know.

The entities/web-app_2_3.dtd might be needed.

The entities/catalog-demo/ is needed by some of
the core samples.

-David

[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

[Gump]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project cocoon has an issue affecting its community integration.
This issue affects 56 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-ajax :  Ajax - Utilities and resources for Ajax applications.
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-captcha :  Utilites to generate simple CAPTCHAs
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-core-samples-additional :  Additional core samples.
- cocoon-block-core-samples-main :  Main core samples.
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A "jcr:" protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-ojb :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-querybean :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-validation :  In-pipeline validation of documents
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- lenya :  Content Management System


Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon]
 -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: 
[cocoon-testcase]
 -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: 
[cocoon-deprecated]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test]
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output
 -WARNING- No directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html
Work Name: build_cocoon_cocoon (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dlogkit.jar=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-14022006.jar
 -Dbuild=build/cocoon-14022006 gump-core 
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH: 
/opt/jdk1.4/lib/t

[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

[Gump]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project cocoon has an issue affecting its community integration.
This issue affects 56 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-ajax :  Ajax - Utilities and resources for Ajax applications.
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-captcha :  Utilites to generate simple CAPTCHAs
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-core-samples-additional :  Additional core samples.
- cocoon-block-core-samples-main :  Main core samples.
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A "jcr:" protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-ojb :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-querybean :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-validation :  In-pipeline validation of documents
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- lenya :  Content Management System


Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon]
 -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: 
[cocoon-testcase]
 -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: 
[cocoon-deprecated]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test]
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output
 -WARNING- No directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html
Work Name: build_cocoon_cocoon (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dlogkit.jar=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-14022006.jar
 -Dbuild=build/cocoon-14022006 gump-core 
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH: 
/opt/jdk1.4/lib/t

Re: another simple Store question

[Ralph Goers]

Yes, you can write your own store. For example, DefaultTransientStore 
extends MRUMemoryStore. If you look in cocoon.roles you will see that 
transient-store and store are defined there.  You can easily create a 
new role to create your own store and then configure it in 
cocoon.xconf.  In fact, you don't even have to define it in cocoon.roles 
if you don't want to (take a look at some other definitions that use the 
 element), it just makes cocoon.xconf a little bit cleaner. 

Once you have your own store configured then just use it instead of one 
of the other stores.


Ralph

Tim Williams wrote:

I need to be able to store null values in the "Store".  I think this
is causing me problems because of MRUMemoryStore.  The MRUMemoryStore
docs say that it's a HashMap implementation which would support my
needs well.  After running out of places to look, I decided to take a
look at its implementation and appears to be Hash*table*
implementation after all, thus apparently causing my problems.

As I described in [1], we're trying to use the store in an input
module but this appears to be a show-stopper.  Can anyone give me an
idea of what to do next?  Is there a store implementation that does
support null values? Is it pluggable like that?  I'm very much still
learning Cocoon and am at the end of where my current knowledge will
take me.  Any pointers would be greatly appreciated...
Thanks,
--tim


[1] - http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113977723621498&w=2
  

another simple Store question

[Tim Williams]

I need to be able to store null values in the "Store".  I think this
is causing me problems because of MRUMemoryStore.  The MRUMemoryStore
docs say that it's a HashMap implementation which would support my
needs well.  After running out of places to look, I decided to take a
look at its implementation and appears to be Hash*table*
implementation after all, thus apparently causing my problems.

As I described in [1], we're trying to use the store in an input
module but this appears to be a show-stopper.  Can anyone give me an
idea of what to do next?  Is there a store implementation that does
support null values? Is it pluggable like that?  I'm very much still
learning Cocoon and am at the end of where my current knowledge will
take me.  Any pointers would be greatly appreciated...
Thanks,
--tim


[1] - http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=113977723621498&w=2

Re: M10N of xmldb and databases blocks

[Daniel Fagerstrom]

Jorg Heymans skrev:

Jean-Baptiste Quenot wrote:


But  where  do  I  put web.xml,  cocoon.xconf  and  sitemap.xmap
customizations?  Is there a M10N documentation available?

Please help.  I  don't know where to put the  xpatch files, I know
that  it works  differently  now,  but cannot  manage  to find  an
example.


I'm a bit out of touch with the block activity lately so don't shoot me
if i'm wrong, but i think this is the first block needing web.xml
modifications for the block to work. I can't remember the mechanism of
how this is supposed to work being discussed. Presumably the deployer
would pick up the necessary modifications and somehow patch these into
the running web.xml.


Why does the DB driver need to be configured as a servlet init-parameter 
in the first place, couldn't it be configured in some component instead?


/Daniel

[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

[Gump]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project cocoon has an issue affecting its community integration.
This issue affects 56 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-ajax :  Ajax - Utilities and resources for Ajax applications.
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-captcha :  Utilites to generate simple CAPTCHAs
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-core-samples-additional :  Additional core samples.
- cocoon-block-core-samples-main :  Main core samples.
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A "jcr:" protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-ojb :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-querybean :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-validation :  In-pipeline validation of documents
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- lenya :  Content Management System


Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon]
 -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: 
[cocoon-testcase]
 -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: 
[cocoon-deprecated]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test]
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output
 -WARNING- No directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html
Work Name: build_cocoon_cocoon (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dlogkit.jar=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-14022006.jar
 -Dbuild=build/cocoon-14022006 gump-core 
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH: 
/opt/jdk1.4/lib/t

[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed

[Gump]

To whom it may engage...

This is an automated request, but not an unsolicited one. For 
more information please visit http://gump.apache.org/nagged.html, 
and/or contact the folk at [EMAIL PROTECTED]

Project cocoon has an issue affecting its community integration.
This issue affects 56 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- cocoon :  Java XML Framework
- cocoon-block-ajax :  Ajax - Utilities and resources for Ajax applications.
- cocoon-block-apples :  Java XML Framework
- cocoon-block-asciiart :  Java XML Framework
- cocoon-block-authentication-fw :  Java XML Framework
- cocoon-block-axis :  Java XML Framework
- cocoon-block-batik :  Java XML Framework
- cocoon-block-bsf :  Java XML Framework
- cocoon-block-captcha :  Utilites to generate simple CAPTCHAs
- cocoon-block-chaperon :  Java XML Framework
- cocoon-block-core-samples-additional :  Additional core samples.
- cocoon-block-core-samples-main :  Main core samples.
- cocoon-block-cron :  Java XML Framework
- cocoon-block-databases :  Java XML Framework
- cocoon-block-deli :  Java XML Framework
- cocoon-block-eventcache :  Java XML Framework
- cocoon-block-fop :  Java XML Framework
- cocoon-block-forms :  Java XML Framework
- cocoon-block-hsqldb :  Java XML Framework
- cocoon-block-html :  Java XML Framework
- cocoon-block-itext :  Java XML Framework
- cocoon-block-javaflow :  Java XML Framework
- cocoon-block-jcr :  A "jcr:" protocol for Cocoon
- cocoon-block-jfor :  Java XML Framework
- cocoon-block-jms :  Java XML Framework
- cocoon-block-jsp :  Java XML Framework
- cocoon-block-linkrewriter :  Java XML Framework
- cocoon-block-lucene :  Java XML Framework
- cocoon-block-mail :  Java XML Framework
- cocoon-block-midi :  Java XML Framework
- cocoon-block-naming :  Java XML Framework
- cocoon-block-ojb :  Java XML Framework
- cocoon-block-paranoid :  Java XML Framework
- cocoon-block-petstore :  Java XML Framework
- cocoon-block-profiler :  Java XML Framework
- cocoon-block-proxy :  Java XML Framework
- cocoon-block-python :  Java XML Framework
- cocoon-block-qdox :  Java XML Framework
- cocoon-block-querybean :  Java XML Framework
- cocoon-block-repository :  Java XML Framework
- cocoon-block-serializers :  Java XML Framework
- cocoon-block-session-fw :  Java XML Framework
- cocoon-block-slop :  Java XML Framework
- cocoon-block-spring-app :  A demo for Spring and Cocoon
- cocoon-block-stx :  Java XML Framework
- cocoon-block-taglib :  Java XML Framework
- cocoon-block-template :  Java XML Framework
- cocoon-block-tour :  Java XML Framework
- cocoon-block-validation :  In-pipeline validation of documents
- cocoon-block-velocity :  Java XML Framework
- cocoon-block-web3 :  Java XML Framework
- cocoon-block-xmldb :  Java XML Framework
- cocoon-block-xsp :  Java XML Framework
- forrest :  Apache Forrest is an XML standards-oriented documentation fr...
- forrest-test :  Apache Forrest is an XML standards-oriented documentation 
fr...
- lenya :  Content Management System


Full details are available at:
http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html

That said, some information snippets are provided here.

The following annotations (debug/informational/warning/error messages) were 
provided:
 -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon]
 -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: 
[cocoon-testcase]
 -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: 
[cocoon-deprecated]
 -INFO- Made directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test]
 -INFO- Failed with reason build failed
 -INFO- Project Reports in: 
/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output
 -WARNING- No directory 
[/usr/local/gump/public/workspace/cocoon/build/cocoon-14022006/test/output]
 -INFO- Failed to extract fallback artifacts from Gump Repository



The following work was performed:
http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html
Work Name: build_cocoon_cocoon (Type: Build)
Work ended in a state of : Failed
Elapsed: 
Command Line: java -Djava.awt.headless=true 
-Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/build/xercesImpl.jar
 org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml 
-Dbuild.sysclasspath=only 
-Dlogkit.jar=/usr/local/gump/public/workspace/excalibur/containerkit/logkit/target/excalibur-logkit-14022006.jar
 -Dbuild=build/cocoon-14022006 gump-core 
[Working Directory: /usr/local/gump/public/workspace/cocoon]
CLASSPATH: 
/opt/jdk1.4/lib/t

Re: M10N of xmldb and databases blocks

[Jorg Heymans]

Jean-Baptiste Quenot wrote:

>> But  where  do  I  put web.xml,  cocoon.xconf  and  sitemap.xmap
>> customizations?  Is there a M10N documentation available?
> 
> Please help.  I  don't know where to put the  xpatch files, I know
> that  it works  differently  now,  but cannot  manage  to find  an
> example.

I'm a bit out of touch with the block activity lately so don't shoot me
if i'm wrong, but i think this is the first block needing web.xml
modifications for the block to work. I can't remember the mechanism of
how this is supposed to work being discussed. Presumably the deployer
would pick up the necessary modifications and somehow patch these into
the running web.xml.

Additional xconf configuration should be picked up automatically, there
is a mechanism in place for this already.

HTH, sorry for being so vague :(

Jorg

Re: Unified directory layout for trunk?

[Jorg Heymans]

Carsten Ziegeler wrote:

>> I'm wondering where  to put the mock classes  for block databases.
>> Where did you put portal's mock classes?
> The portals block has no mocks in 2.2 :) I think you're approach for the
> mocks is valid. What do others think?
>

Initially, I thought we could keep all our mocks in ./cocoon-mocks. This
would avoid the overhead of having to create and manage a separate
block/pom for the sake of a few empty classes.

Jean-Baptiste's approach however works equally well.


Jorg

DO NOT REPLY [Bug 32128] - CompilingClassLoader !extends URLClassLoader: JspGenerator doesn't work from flow but does otherwise...

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32128


[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

src/webapp/WEB-INF/entities

[Jean-Baptiste Quenot]

Hello,

I would like to know what purpose serves the existing resources in
webapp/WEB-INF/entities?  I know that one can setup a catalog for
resolving entities, but I'm talking about all the stuff: DTDs,
schemas, etc.  Is it really useful for a mean web application?

In the README, there is a message that I don't understand:

« Please keep these resources in sync with the authoritative stuff
at Forrest. »

I'm proposing to add a build option to avoid copying all these
often-unnecessary resources.

WDYT?
-- 
Jean-Baptiste Quenot
http://caraldi.com/jbq/

Re: blog.wyona.com down

[Oliver Schalch]

wrong list, sorry!

blog.wyona.com down

[Oliver Schalch]

Hi,

Since we had the Vserver1 to reboot 2 weeks ago, the Blog publication 
http://blog.wyona.com isnt up anymore.
I could it restart but  that will eat more memory and the blog is not so 
important I guess until better Hardware.


top - 15:41:42 up 19 days,  1:23,  0 users,  load average: 1.89, 5.06, 5.04
Tasks:   9 total,   1 running,   8 sleeping,   0 stopped,   0 zombie
Cpu(s):  0.3% us,  0.0% sy,  0.0% ni, 99.7% id,  0.0% wa,  0.0% hi,  0.0% si
Mem:   1946284k total,  1862312k used,83972k free,   181892k buffers
Swap:   497972k total,   497956k used,   16k free,   288476k cached

There is again almost all swap + memory in use.

I will *not* turn blog publication on :)

Oliver


--
Oliver Schalch   [EMAIL PROTECTED]
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com  http://lenya.apache.org 

Re: New skin for web site

[hepabolu]

Ross Gardler wrote:

David Crossley wrote:

hepabolu wrote:

BTW do you like the layout of the Notes, Warnings and Fixes? (See 
samples page)



The main trouble that i see, is that it puts each "note"
out-of-context with the main page, i.e. not sure what the
warning refers to.


Thanks David, I meant to say that, but it got lost in the last few days 
work. I also feel the context of the note/waring/fixme has been lost, 
i.e. it is no longer attached to the paragraph that it followed.


I know, I realised that too, but OTOH usually people will skim pages for 
information. Notes/warnings/fixme-s will stand out and will probably 
read out of context anyway. So I'd rather go for clear information in 
such a box than depending on the context of the box. Much like the rule 
that in a paragraph you should not refer to the title but include it in 
the sentence.


On subsequent reads these boxes are only in the way of the natural flow 
of the information and can cause irritation.



Otherwise great. Thanks for your excellent work.


+1


Thanks. It was great fun to do.

Bye, Helma

Re: AW: How to use cocoon servlet only for rendering documents?

[Bertrand Delacretaz]

...Your are refering to the jakarta commons httpclient library?...


yes.

-Bertrand

smime.p7s
Description: S/MIME cryptographic signature

AW: How to use cocoon servlet only for rendering documents?

[Peter Neu]

Yes, that sounds good. 
Your are refering to the jakarta commons httpclient library?

I suppose a one way communication will suffice for the first iteration. I'm
thinking of just sendig the usual http attachment header back from cocoon
instead of from my client code. So the user will only see the url in the
attachment window.

Cheers,
Pete



-Ursprüngliche Nachricht-
Von: Bertrand Delacretaz [mailto:[EMAIL PROTECTED] 
Gesendet: Dienstag, 14. Februar 2006 10:58
An: dev@cocoon.apache.org
Betreff: Re: How to use cocoon servlet only for rendering documents?

Le 14 févr. 06, à 10:40, Peter Neu a écrit :

> ...I have the use case that I want to combine Cocoon with another 
> framework say
> Struts (there is lots of legacy code). I want to do all the web front 
> end
> work with Struts and do the rendering of pdf, xml, excel etc with 
> Cocoon...

A nicely decoupled way of doing this is by using an HTTP client in your 
Struts (or whatever) code: run Cocoon in a separate servlet, even on a 
different host if it's useful, and have your other module send XML data 
to Cocoon via HTTP POST, receive the results and proxy them to the web 
client.

You could use the httpclient java library to do this, it's not that 
much code to write, and if you do it right you can keep it all 
streaming without having to buffer data in memory, so it would be 
efficient (not as much as a more tightly coupled solution, but if 
you're talking about generating PDF it's not the communications costs 
that will be a problem).

Such a client could be a welcome addition to Cocoon, if you want to go 
this route I'll try to find some time to help and possibly integrate 
the client in a future relelase.

-Bertrand

Re: How to use cocoon servlet only for rendering documents?

[Bertrand Delacretaz]

Le 14 févr. 06, à 10:40, Peter Neu a écrit :

...I have the use case that I want to combine Cocoon with another 
framework say
Struts (there is lots of legacy code). I want to do all the web front 
end
work with Struts and do the rendering of pdf, xml, excel etc with 
Cocoon...


A nicely decoupled way of doing this is by using an HTTP client in your 
Struts (or whatever) code: run Cocoon in a separate servlet, even on a 
different host if it's useful, and have your other module send XML data 
to Cocoon via HTTP POST, receive the results and proxy them to the web 
client.


You could use the httpclient java library to do this, it's not that 
much code to write, and if you do it right you can keep it all 
streaming without having to buffer data in memory, so it would be 
efficient (not as much as a more tightly coupled solution, but if 
you're talking about generating PDF it's not the communications costs 
that will be a problem).


Such a client could be a welcome addition to Cocoon, if you want to go 
this route I'll try to find some time to help and possibly integrate 
the client in a future relelase.


-Bertrand


smime.p7s
Description: S/MIME cryptographic signature

Re: New skin for web site

[Ross Gardler]

David Crossley wrote:

hepabolu wrote:

BTW do you like the layout of the Notes, Warnings and Fixes? (See 
samples page)



The main trouble that i see, is that it puts each "note"
out-of-context with the main page, i.e. not sure what the
warning refers to.


Thanks David, I meant to say that, but it got lost in the last few days 
work. I also feel the context of the note/waring/fixme has been lost, 
i.e. it is no longer attached to the paragraph that it followed.



Otherwise great. Thanks for your excellent work.


+1

Ross

How to use cocoon servlet only for rendering documents?

[Peter Neu]

Hello,

I already posted this question in the dev list but nobody responded so I put
it here.

I have the use case that I want to combine Cocoon with another framework say
Struts (there is lots of legacy code). I want to do all the web front end
work with Struts and do the rendering of pdf, xml, excel etc with Cocoon.
Thus I want pass parameters to the Cocoon servlet and then let cocoon query
data from the database and then render the stuff. I would only need the
basic functionality to render the documents and the SQLTransformer. Is this
possible?

I heared some talk about the Paranoid cocoon servlet but I don't really
understand how this fits in. Can somebody please explain or tell me where to

find information on this?

Cheers,
Pete

Re: M10N of xmldb and databases blocks

[Jean-Baptiste Quenot]

* Jean-Baptiste Quenot:

> But  where  do  I  put web.xml,  cocoon.xconf  and  sitemap.xmap
> customizations?  Is there a M10N documentation available?

Please help.  I  don't know where to put the  xpatch files, I know
that  it works  differently  now,  but cannot  manage  to find  an
example.
-- 
Jean-Baptiste Quenot
http://caraldi.com/jbq/