RE: XUpdate questions
Title: RE: XUpdate questions The Xupdate functionality comes with the xindice database. (See the wiki for more information on how to integrate xindice). Jon -Original Message- From: jm [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 01, 2003 9:43 AM To: [EMAIL PROTECTED] Subject: XUpdate questions hi all, i have one complex xml-document which i want to edit via my webbrowser with some kinds of forms so i don't really need a heavy CMS. i read about xmlforms, xforms and then i came across XUpdate which sounds like that i'm looking for. (but i would be glad about any system which is easy to use instead of XUpdate either) so the first problem is, that i don't realy know how to install and use the XUpdate functionality into my cocoon 2.0.4. i would be glad if anybody could help me or give me a hint where to find further information. regards, jm - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: reading xml from pipeline into a flow script
Title: RE: reading xml from pipeline into a flow script
One simple way of accomplishing this is to simply, define pipeline to generate, transform, and serialize the xml. Then, in the flowscript, simply use the jaxp dom api to load the generated xml:
flow() {
var document = Packages.javax.xml.parsers.DocumentBuilderFactory.newInstance().newDocumentBuilder().build(http://uri-to-xml-file);
...
document.getDocumentElement();
// it is now a dom
}
-Original Message-
From: Simon Price [mailto:[EMAIL PROTECTED]]
Sent: Saturday, June 28, 2003 3:25 PM
To: [EMAIL PROTECTED]
Subject: reading xml from pipeline into a flow script
From within a flow script, I would like to read (or pass in) xml
generated by a series of pipeline xslt transformations.
Please could someone give me a pointer on how to do this?
Cheers
Simon
---
Simon Price
Institute for Learning and Research Technology
University of Bristol
8-10 Berkeley Square
Bristol BS8 1HH
United Kingdom
Direct: +44 (0)7071 226 720
Office: +44 (0)117 928 7193
Fax: +44 (0)117 928 7112
[EMAIL PROTECTED]
http://www.ilrt.bristol.ac.uk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Continuations and JXForms
Title: RE: Continuations and JXForms JD I am not an official cocoon developer, but I believe the continuation id is generated the first time a user visits any page in the flowscript, not just the final submission. Jon -Original Message- From: JD Daniels [mailto:[EMAIL PROTECTED]] Sent: Monday, June 16, 2003 2:21 PM To: [EMAIL PROTECTED] Subject: Continuations and JXForms Is there some little snip of code for the form that I haven't found in the docs to make this work? Here is my trouble: Display the form. Click next --Errors Repair Errors--click next all is good. (Or success and display results. Errors on the form make no difference) Display the form Click next --Errors (Or success and display results. Errors on the form make no difference) click The back Button on the browser to go back too the form.. fill it out again Invalid continuation error. I was thinking the continuation id was generated when the form is submitted. Should it not generate a new one if the user goes back to the form and resubmits it? Cocoon2.1m3 dev june 15 7:00pm Linux redhat 7.3 Sun Java sdk 1.4.01 JD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Calling Actions from the Flow with Javascript
Title: RE: Calling Actions from the Flow with Javascript I have experienced this, as well. Jon -Original Message- From: Bobby Mitchell [mailto:[EMAIL PROTECTED]] Sent: Monday, June 09, 2003 12:49 PM To: [EMAIL PROTECTED] Subject: Calling Actions from the Flow with _javascript_ I have been able to call an action that has been declared in the root sitemap, but not from my sub-sitemap. Has this problem, http://marc.theaimsgroup.com/?l=xml-cocoon-users=105171947003418=2, been looked at further? Bobby M - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
questions regarding v2.1
Title: questions regarding v2.1 I have been developing a webapp with cocoon 2 for at least three months now. After building the latest system (as checked out from the repository cocoon-2.1), xmlform does not appear to be mentioned in the sitemap, but the java classes have all been built. Is this intentional? Jon
RE: extending XMLForms for different kinds of models...opinions?
Title: RE: extending XMLForms for different kinds of models...opinions? Ivelin The W3C's candidate recommendation for xforms defines both: 1. a element named 'model' enabling one to bind an object to a named model in the form 2. a common attribute named 'model' enabling one to choose which model to bind an xforms control to Basically, the idea would be to change the existing one-to-one relationship between a form and its model to a one-to-many. I could see an advantage in keeping a primary model for each form, but still allow for multiple models to be referenced. The primary value I see in this approach is the ability to easily pull data from multiple sources. Example: I am currently in the development of a project using cocoon/xmlforms as the front-end and xindice as the back-end. In order to pull data from the xindice database into my xmlforms, I currently have my javabean model set up with a field referencing a class that returns a jxpath Container which connects to the Xindice database. If multiple models were supported by xmlform, I could more easily separate the database data from the form/input data. Jon -Original Message-From: ivelin [mailto:[EMAIL PROTECTED]]Sent: Saturday, February 15, 2003 9:30 PMTo: [EMAIL PROTECTED]; 'Josema Alonso 'Subject: Re: extending XMLForms for different kinds of models...opinions? Jonathan, please elaborate on the multiple models requirement. I think that Josema's idea is a significant step forward. It does not prohibit future extensions, so I definitely support it, but in the meanwhile I am interested to hear what else can we do in the future. -=Ivelin=- - Original Message - From: Jonathan Spaeth To: 'Josema Alonso ' ; 'Cocoon-Users ' Sent: Saturday, February 15, 2003 1:00 PM Subject: RE: extending XMLForms for different kinds of models...opinions? As a user of cocoon, I see this as a very advantageous feature. I am currently using cocoon/xmlform and have been developing with it for about five months now. Your suggestion matches some of the thoughts I was having at the start of my project while I was becoming accustomed to using the framework. I have taken advantage of the javabean architecture in the sense that I can dynamically grab data from different data sources, but I agree in the simple cases an xml model would be well-suited. Another suggestion I would have is to allow for multiple models. The W3C spec for xforms has been designed around multiple models; if a second revision of xmlforms is in the works, I would suggest investigating this feature. Jon -Original Message- From: Josema Alonso To: Cocoon-Users Sent: 2/15/03 11:39 AM Subject: Re: extending XMLForms for different kinds of models...opinions? Jeremy, I posted here cause I wanted to know if the users would like that feature to be added. I thought the dev list would be more suitable in case of discussing the way of implementing it. Since I'm not currently subscribed to the dev list, feel free to cc the message there if you want to. Btw, glad you like it. Thanks. - Original Message - From: "Jeremy Quinn" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 11:24 AM Subject: Re: extending XMLForms for different kinds of models...opinions? On Friday, February 14, 2003, at 01:07 PM, Josema Alonso wrote: Dear all, I need your suggestions and opinions in extending the current XMLForm model approach. If you use XMLForm or are thinking about using it soon, I'd suggest youy to read this message and send some feedback to the list. snip/ Would it not be best to discuss this on Cocoon-Dev? Very nice idea, BTW! regards Jeremy - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: extending XMLForms for different kinds of models...opinions?
Title: RE: extending XMLForms for different kinds of models...opinions? As a user of cocoon, I see this as a very advantageous feature. I am currently using cocoon/xmlform and have been developing with it for about five months now. Your suggestion matches some of the thoughts I was having at the start of my project while I was becoming accustomed to using the framework. I have taken advantage of the javabean architecture in the sense that I can dynamically grab data from different data sources, but I agree in the simple cases an xml model would be well-suited. Another suggestion I would have is to allow for multiple models. The W3C spec for xforms has been designed around multiple models; if a second revision of xmlforms is in the works, I would suggest investigating this feature. Jon -Original Message- From: Josema Alonso To: Cocoon-Users Sent: 2/15/03 11:39 AM Subject: Re: extending XMLForms for different kinds of models...opinions? Jeremy, I posted here cause I wanted to know if the users would like that feature to be added. I thought the dev list would be more suitable in case of discussing the way of implementing it. Since I'm not currently subscribed to the dev list, feel free to cc the message there if you want to. Btw, glad you like it. Thanks. - Original Message - From: Jeremy Quinn [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, February 15, 2003 11:24 AM Subject: Re: extending XMLForms for different kinds of models...opinions? On Friday, February 14, 2003, at 01:07 PM, Josema Alonso wrote: Dear all, I need your suggestions and opinions in extending the current XMLForm model approach. If you use XMLForm or are thinking about using it soon, I'd suggest youy to read this message and send some feedback to the list. snip/ Would it not be best to discuss this on Cocoon-Dev? Very nice idea, BTW! regards Jeremy - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xmlform samples are not working for me
Title: xmlform samples are not working for me I just checked out the latest version of the repository and found the xmlform samples are not working for me: Here is the stack trace. Has anybody seen this or know what it could be related to? java.lang.NullPointerException: at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.validatePipeline(AbstractCachingProcessingPipeline.java:424) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:545) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:497) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:463) at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:148) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.ActTypeNode.invoke(ActTypeNode.java:158) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:153) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:143) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:317) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:299) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:134) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:153) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:143) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:317) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:299) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:134) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:84) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:164) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:153) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:108) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:143) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:317) at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:299) at org.apache.cocoon.Cocoon.process(Cocoon.java:600) at org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1104) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at
RE: building the current CVS
Title: RE: building the current CVS I had a similar problem when attempting this with jdk 1.3.1 on a unix system. The problem is java vm is running out of memory. The solution is to increase the memory allocated to the java vm. This can be done by passing -Xmx to the java vm or -X for the -X options. Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 2:01 AM To: [EMAIL PROTECTED] Subject: building the current CVS Hi. There are a problem building the current CVS version (13.01.2003) for a JDK1.3.1_06 under Windows 2000. Apart from the known problem based on the missing mail.jar, I receive a log trace ...: .. ... prepare-webapp-scratchpad: [xconf-tool] Reading: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\sitemap.xmap [xconf-tool] No Changes: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\sitemap.xmap [xconf-tool] Reading: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\sitemap.xmap [xconf-tool] No Changes: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\sitemap.xmap [xconf-tool] Reading: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\WEB-INF\cocoon.xconf [xconf-tool] Processing: E:\cocoon\xml-cocoon2_20030113\build\cocoon\scratchpad\src\org\apache\cocoon\components\source\blob.xconf [xconf-tool] Processing: E:\cocoon\xml-cocoon2_20030113\build\cocoon\scratchpad\src\org\apache\cocoon\components\source\impl\sourceinspector.xconf [xconf-tool] Processing: E:\cocoon\xml-cocoon2_20030113\build\cocoon\scratchpad\src\org\apache\cocoon\transformation\pagination\Paginator.xconf [xconf-tool] Writing: E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\WEB-INF\cocoon.xconf [copy] Copying 210 files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp [copy] Copied 34 empty directories to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp [copy] Copying 10 files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp compile-samples: [mkdir] Created dir: E:\cocoon\xml-cocoon2_20030113\build\cocoon\classes\samples [javac] Compiling 2 source files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\classes package-samples: [jar] Building jar: E:\cocoon\xml-cocoon2_20030113\build\cocoon\cocoon-samples.jar copy-tools-lib: copy-webapp-libs: [copy] Copying 29 files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\WEB-INF\lib [copy] Copying 34 files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\WEB-INF\lib [copy] Copying 22 files to E:\cocoon\xml-cocoon2_20030113\build\cocoon\webapp\WEB-INF\lib BUILD FAILED java.lang.OutOfMemoryError no stack trace available Total time: 3 minutes 7 seconds java.lang.OutOfMemoryError no stack trace available Regards, Adriano Zigante - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cocoon 2.1 and sunshine
Title: Cocoon 2.1 and sunshine I have noticed that the sunshine authentication and portal packages are not in cocoon 2.1 in cvs. Has this functionality been moved elsewhere or is it going to be? I would like to use the authentication andportal frameworks, as well as the xmlform framework; however, as things currently seem, xmlform is contained in 2.1 and not 2.0 and sunshine is contained in 2.0 and not 2.1. Any thoughts or plans? Thanks in advance, Jon
Multiple data sources
Title: Multiple data sources Is there a standard way of integrating multiple data sources using xmlform? The XForms spec defines the model and instance elements which would be a good solution for my problem. Basically, this is what I am attempting to do: 1. Load an xml document from an xml database (xindice); 2. Perform an xpath expression on this data and loop over the resulting expression, using the itemset ref=//group[@id='switches']/ tag; however the xpath context for this expression should be the document loaded from the database, not the xforms document itself. Are multiple models supported using xforms or should I just define a standard model Bean and load all of my xml database data into the Bean upon instantiation? Thanks, Jon
