RE: Tree Widget, child ordering
So I ventured into the Java source The DefaultTreeModel uses a HashTable, hence the un-orderdness. I was able to create a specialize TreeModel using a Vector that maintains child ordering. From: Combinational Logic [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 24, 2006 4:26 AM To: users@cocoon.apache.org Subject: Tree Widget, child ordering For the Tree Widget, Im having some trouble with node ordering under a flowscript-built DefaultTreeModel. The ordering does not seem to be correlated with the key or the order in which nodes are added. Im not sure if this is to be expected or if Im doing something wrong. Thanks, CL
RE: Dojo-based forms samples
Seems putting a div inside each tree node is a workaround. Thanks Sylvain for pointing me to the bug collector, Ill now look there first before spamming the list. From: Combinational Logic [mailto:[EMAIL PROTECTED]] Sent: Friday, June 23, 2006 11:58 AM To: users@cocoon.apache.org Cc: [EMAIL PROTECTED] Subject: Re: Dojo-based forms samples Any update / fix wrt the Dojo tree-table issue mentioned here: http://www.mail-archive.com/dev@cocoon.apache.org/msg42132.html If not, any hints regarding how one might track down the issue. Thanks, CL
Tree Widget collapse / expand all
I'm trying to create links in a form template that will 'collapse all' and 'expand all' for a tree widget instance (with ajax). I tried the following and various other combinations with no luck. Any tips? p[a href=# onclick=return TreeToggleCollapse('${widget.fullName}', '*')collapse all/a]/p Thanks, CL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dojo-based forms samples
Any update / fix wrt the Dojo tree-table issue mentioned here: http://www.mail-archive.com/dev@cocoon.apache.org/msg42132.html If not, any hints regarding how one might track down the issue. Thanks, CL
xmldb query on Cocoon 2.1.9 = error; works on 2.1.7
Hi Cocooners, Recently I updated from cocoon-2.1.7 to 2.1.9. On 2.1.7 I had xmldb (xindice) working fine, but with 2.1.9 I've got problems. The problem can be observed in the xmldb block samples at: http://localhost:/samples/blocks/xmldb/welcome On this page the 'Query Collection' and 'Query Resource' links produce an error. All other links on the page work as expected. The xmldb, databases, and xsp blocks are included for my build. JVM is 1.4.2. Any help would be greatly appreciated. Thanks, CL The error printed to the browser is as follows: HTTP ERROR: 500 org%2Eapache%2Expath%2Ecompiler%2ECompiler%2E%3Cinit%3E%28Ljavax%2Fxml%2Ftra nsform%2FErrorListener%3BLjavax%2Fxml%2Ftransform%2FSourceLocator%3B%29V The error and stack trace printed to the terminal is as follows: 23:39:29.918 WARN!! Error for /samples/blocks/xmldb/db/cocoon/samples.xml?xpath= /samples/group java.lang.NoSuchMethodError: org.apache.xpath.compiler.Compiler.init(Ljavax/xm l/transform/ErrorListener;Ljavax/xml/transform/SourceLocator;)V at org.apache.xindice.core.query.XPathQueryResolver$XPathQuery.init(XP athQueryResolver.java:163) at org.apache.xindice.core.query.XPathQueryResolver.query(XPathQueryReso lver.java:130) at org.apache.xindice.core.query.QueryEngine.query(QueryEngine.java:122) at org.apache.xindice.core.Collection.queryDocument(Collection.java:1242 ) at org.apache.xindice.client.xmldb.embed.CollectionImpl.query(Collection Impl.java:438) at org.apache.xindice.client.xmldb.services.QueryService.queryResource(Q ueryService.java:70) at org.apache.cocoon.components.source.impl.XMLDBSource.queryToSAX(XMLDB Source.java:372) at org.apache.cocoon.components.source.impl.XMLDBSource.resourceToSAX(XM LDBSource.java:299) at org.apache.cocoon.components.source.impl.XMLDBSource.toSAX(XMLDBSourc e.java:273) at org.apache.cocoon.components.source.SourceUtil.toSAX(SourceUtil.java: 100) at org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java: 320) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.jav a:115) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.proc essXMLPipeline(AbstractProcessingPipeline.java:578) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingP ipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:281) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.proc ess(AbstractProcessingPipeline.java:480) at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invo ke(SerializeNode.java:120) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(M atchNode.java:107) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNod e.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invok e(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invo ke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.proc ess(ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.proc ess(ConcreteTreeProcessor.java:176) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(Tree Processor.java:252) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(M ountNode.java:117) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNod e.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invok e(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invo ke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.proc ess(ConcreteTreeProcessor.java:234) at
FW: The Collection Query and Resource Query examples in Cocoon 2.1.9 don't work in the xmldb Block
Looks like the 2.1.9 xmldb issue (mentioned in my previous post) was already identified... Anyone know of a fix or work-around, or have recommendations on how I might debug / track down this issue? Thanks, CL -Original Message- From: H.H.Braun [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 8:38 AM To: users@cocoon.apache.org Subject: The Collection Query and Resource Query examples in Cocoon 2.1.9 don't work in the xmldb Block I get a NoSuchMethodError for org.apache.xpath.compiler.Compiler - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: xmldb query on Cocoon 2.1.9 = error; works on 2.1.7
Thanks Antonio for your recommendation. I managed to get it working (without modifying any source) as follows: 1) checked out the most recent xindice from SVN 2) built xindice 3) replaced cocoon-2.1.9\build\webapp\WEB-INF\lib\xindice-1.1b4.jar with xindice-1.1b5-dev.jar -Original Message- From: Combinational Logic [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 21, 2006 12:14 AM To: users@cocoon.apache.org Subject: xmldb query on Cocoon 2.1.9 = error; works on 2.1.7 Hi Cocooners, Recently I updated from cocoon-2.1.7 to 2.1.9. On 2.1.7 I had xmldb (xindice) working fine, but with 2.1.9 I've got problems. The problem can be observed in the xmldb block samples at: http://localhost:/samples/blocks/xmldb/welcome On this page the 'Query Collection' and 'Query Resource' links produce an error. All other links on the page work as expected. The xmldb, databases, and xsp blocks are included for my build. JVM is 1.4.2. Any help would be greatly appreciated. Thanks, CL The error printed to the browser is as follows: HTTP ERROR: 500 org%2Eapache%2Expath%2Ecompiler%2ECompiler%2E%3Cinit%3E%28Ljavax%2Fxml%2Ftra nsform%2FErrorListener%3BLjavax%2Fxml%2Ftransform%2FSourceLocator%3B%29V The error and stack trace printed to the terminal is as follows: 23:39:29.918 WARN!! Error for /samples/blocks/xmldb/db/cocoon/samples.xml?xpath= /samples/group java.lang.NoSuchMethodError: org.apache.xpath.compiler.Compiler.init(Ljavax/xm l/transform/ErrorListener;Ljavax/xml/transform/SourceLocator;)V at org.apache.xindice.core.query.XPathQueryResolver$XPathQuery.init(XP athQueryResolver.java:163) at org.apache.xindice.core.query.XPathQueryResolver.query(XPathQueryReso lver.java:130) at org.apache.xindice.core.query.QueryEngine.query(QueryEngine.java:122) at org.apache.xindice.core.Collection.queryDocument(Collection.java:1242 ) at org.apache.xindice.client.xmldb.embed.CollectionImpl.query(Collection Impl.java:438) at org.apache.xindice.client.xmldb.services.QueryService.queryResource(Q ueryService.java:70) at org.apache.cocoon.components.source.impl.XMLDBSource.queryToSAX(XMLDB Source.java:372) at org.apache.cocoon.components.source.impl.XMLDBSource.resourceToSAX(XM LDBSource.java:299) at org.apache.cocoon.components.source.impl.XMLDBSource.toSAX(XMLDBSourc e.java:273) at org.apache.cocoon.components.source.SourceUtil.toSAX(SourceUtil.java: 100) at org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java: 320) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.jav a:115) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.proc essXMLPipeline(AbstractProcessingPipeline.java:578) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingP ipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:281) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.proc ess(AbstractProcessingPipeline.java:480) at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invo ke(SerializeNode.java:120) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(M atchNode.java:107) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNod e.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invok e(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invo ke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.proc ess(ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.proc ess(ConcreteTreeProcessor.java:176) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(Tree Processor.java:252) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(M ountNode.java:117) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNod e.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNo de.invokeNodes(AbstractParentProcessingNode.java:68
RE: Updating Xindice with Request Data
Sorry I dont have time to describe all the details, but a brief overview of what worked for me follows: Use flow to display and bind the CForm to the results of an xmldb query then save the results back to a document. Pass the document to a JX pipeline to get it back into the pipeline, then use XSLT to generate stuff in the XUpdate namespace and pass it through an XMLDB transformer. It would be nice to package /abstract this sort of operation up as it seems to be a re-occurring design pattern At least it was for my cocoon development. Perhaps someone knows of a better way. Thoughts? CL From: Mike Casey [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 5:10 PM To: users@cocoon.apache.org Subject: Updating Xindice with Request Data Hi All, I am currently working on an implementation of a wiki type site that uses XML for Wiki syntax, partly to help learn NXBs/Cocoon and partly because I could not find a suitable product out there to meet my needs. The XMLDB block samples has some good examples on how to update Xindice using XML files which is all very well in good however I need to figure out how to pull xml data out of a CForm and then push it into Xindice. The sample has the pipeline map:match pattern=populate map:generate src=""> map:transform type=cinclude/ map:transform type=xmldb/ map:serialize/ /map:match Where ofcourse the generator looks for a physical xml file. Does anyone have any hints on how I might acheive this? I am reasonably new to Cocoon so forgive me if the answer you return is blatantly obvious! Cheers, Mike Casey Wellington New Zealand
web-application distribution
So I've created a cocoon web-application and want to distribute it to a non-developer type (the user) for use by localhost only. I want this to be as easy as possible for the user to install. Any recommendations? Here are some of my ideas: 1) Put the files that I have created (i.e. sitemap, XSLT and js) in a directory on a CD and give this to the user. Then have the user download and build cocoon, and reference the sitemap mount-table.xml 2) Put the cocoon/build/webapp/WEB-INF, cocoon/tools/jetty, cocoon/legal directories and mount-table.xml onto a CD. Is there other stuff that would need to be included? Thanks for your help. CL - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Generating XSD documentation in Cocoon
XSLT from http://titanium.dstc.edu.au/xml/xs3p/ looks like it should do the trick. Thanks to the Vancouver XML users group for this link. From: Combinational Logic [mailto:[EMAIL PROTECTED] Sent: Sunday, November 27, 2005 3:17 PM To: users@cocoon.apache.org Subject: Generating XSD documentation in Cocoon Given a set of XSD files, is there any Cocoon source available (likely XSLT) that enables navigation of the XSD using a high-level hyperlinked view. Im looking for something similar to the schema documentation generated by XML-Spy. Thanks, CL
Generating XSD documentation in Cocoon
Given a set of XSD files, is there any Cocoon source available (likely XSLT) that enables navigation of the XSD using a high-level hyperlinked view. Im looking for something similar to the schema documentation generated by XML-Spy. Thanks, CL
RE: Does cocoon support Word .doc as output format
I think Docbook XML --XSLT-- HTML + CSS imports into word relatively well, but isn't exactly .doc output format. -Original Message- From: Stavros Kounis [mailto:[EMAIL PROTECTED] Sent: Friday, November 25, 2005 11:20 AM To: users@cocoon.apache.org Subject: Re: Does cocoon support Word .doc as output format is .rtf format enough for your needs? 2005/11/25, dcausevi [EMAIL PROTECTED]: I need to convert XML files to Word .doc format, can I do it with cocoon? Thanx Dzenan Causevic Software Developer NaviSite, Inc Syracuse, NY - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stavros S. Kounis Osmosis networks consulting http://www.osmosis.gr Read my weblog at http://tools.osmosis.gr/blog - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Cocoon 2.1.8 - namespaced xml binding failing.
Namespaces gave me major headaches with JX, CFORMS and XMLDb. Seems it would be nice if one could define/overload namespaces on a per-sitemap or per-pipeline basis. Is there a way to do this sort of thing or would this be a bad-practice? A couple of other related questions: i) What is the best way to debug namespace problems? ii) How does one remove the cform view-links from the top right corner? Your wisdom is most-appreciated Cocoon enthusiats. -Original Message- From: Jean-Baptiste Quenot [mailto:[EMAIL PROTECTED] Sent: Friday, October 21, 2005 12:51 AM To: users@cocoon.apache.org Subject: Re: Cocoon 2.1.8 - namespaced xml binding failing. * Suzan Foster: Correction to my previous post: when the prefixes in the xml file and xpath expressions match it does bind, But when f.i. the xml file binds the namespace to the prefix co: whilst the binding definition binds the namespace to the prefix ab: it fails. That's interesting. But can you provide a sample XML document and your form binding? It may be useful to see how you declared the namespaces. -- Jean-Baptiste Quenot Systèmes d'Information ANYWARE TECHNOLOGIES Tel : +33 (0)5 61 00 52 90 Fax : +33 (0)5 61 00 51 46 http://www.anyware-tech.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: DITA and Cocoon
Given that there is widespread interest for something like this, how would you recommend we move ahead? Collaboratively capturing requirements and use-cases for a DITA app seems like a good place to start. Lenya or Daisy might make good starting points, or perhaps it would be best to start from scratch. In terms of cocoon technology my preference is XMLDB + CFORMS. Hibernate might be appropriate too for persistence, but since DITA is XML-based why would one want to work in the object-model realm? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Return xml from an Action to the pipeline?
Having never created a generator, I can't comment on that, but it sounds like a good idea. Can anyone estimate how much effort this requires? Another way might be call the java lib from flowscript, creating a DOM. Then pass the DOM to a JXTemplate (along with any other DOMs you want to 'merge' with). The flowscript would look as follows: var reportDom = Way.To.Create.Dom.From.Some.Java.Lib(); var otherDom = Way.To.Load.Your.Other.Dom(); cocoon.sendPage(merge-jxpipe, {reportDom : reportDom, otherDom: otherDom } ); The JXTemplate could be as simple as the following: to-merge report #{reportDom/*} /report other #{otherDom/*} /other /to-merge Then you could use XSLT to do the merge. Lachlan Paterson wrote: ... So, Jasper Reports aside, my question (assuming the above method is sound) is a more general 2 part question: 1) How do I return xml from an Action and access it in the pipeline? 2) How to I merge that xml document into the one that the pipeline is processing? Actions should not return XML. Why not write a generator instead? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Return xml from an Action to the pipeline?
I think this would be possible with cinclude. Each generator would have its own pipeline. One of your generators would generate cinclude tags that pull in XML from the other generator/pipeline. From: Lachlan Paterson [mailto:[EMAIL PROTECTED] Sent: Sunday, October 16, 2005 3:39 PM To: users@cocoon.apache.org Subject: Re: Return xml from an Action to the pipeline? Is it possible to have two generators and then merge the results? On 10/16/05, Combinational Logic [EMAIL PROTECTED] wrote: Having never created a generator, I can't comment on that, but it sounds like a good idea.Can anyone estimate how much effort this requires? Another way might be call the java lib from flowscript, creating a DOM. Then pass the DOM to a JXTemplate (along with any other DOMs you want to 'merge' with).The flowscript would look as follows: var reportDom = Way.To.Create.Dom.From.Some.Java.Lib(); var otherDom = Way.To.Load.Your.Other.Dom(); cocoon.sendPage(merge-jxpipe, {reportDom : reportDom, otherDom: otherDom } ); The JXTemplate could be as simple as the following: to-merge report #{reportDom/*} /report other #{otherDom/*} /other /to-merge Then you could use XSLT to do the merge. Lachlan Paterson wrote: ... So, Jasper Reports aside, my question (assuming the above method is sound) is a more general 2 part question: 1) How do I return xml from an Action and access it in the pipeline? 2) How to I merge that xml document into the one that the pipeline is processing? Actions should not return XML. Why not write a generator instead? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DITA and Cocoon
The Darwin Information Typing Architecture (DITA) is an OASIS XML standard for technical documentation created by IBM. Im wondering if anyone on this list is/has/or is interested in creating a DITA wiki-like knowledge system upon Cocoon using XMLDB and CForms? I did some searching and couldnt find anything mixing DITA and Cocoon quite surprising since this seems like a natural fit. Some links on DITA http://www-128.ibm.com/developerworks/xml/library/x-dita1/ http://dita-ot.sourceforge.net/ http://docs.oasis-open.org/dita/v1.0/langspec/ditaref-type.toc.html