Re: Status on Woody--CocoonForms renaming
Bruno Dumon wrote: On Sun, 2004-03-07 at 17:43, Joerg Heinicke wrote: On 06.03.2004 19:09, Reinhard Pötz wrote: The first part is done - which means: - renaming of all Java classes - reflect changes within Flowscripts - first run on updating all samples open - Stylesheet for namespace change and change the namespaces As nagoya seems to down at the moment you can find the stylesheet attached. 2 minor issues does it have: - the old problem of namespace clean up. It copies all namespace declarations from input to output, so also the old woody one's. Instead of using xsl:copy I could have used xsl:element, but you need to define then all needed namespaces in the stylesheet additionally starting with i18n, maybe xhtml and so on. I prefer the post-processing (removing the superflouos woody namespaces) over the pre-processing of the stylesheet as adding additional namespace declarations is more error prone than removing the old ones. - whitespace-only text nodes (other must not be there) between comment nodes are removed when they occur outside the root element. That's a problem of Xalan. Inside the root element those text nodes are copied to the output too. I saw this for form1-bind-bean.xml. Wouldn't a simple text based search-and-replace be simpler then an XSLT? Yes, but I want to provide an Ant task for our users which will do the transformation. This can also be the infrastructure for future updates between different CocoonForms versions. Ant the stylesheet written by Jörg looks pretty simple ;-) -- Reinhard
Re: Status on Woody--CocoonForms renaming
On 06.03.2004 19:09, Reinhard Pötz wrote:
The first part is done - which means:
- renaming of all Java classes
- reflect changes within Flowscripts
- first run on updating all samples
open
- Stylesheet for namespace change and change the
namespaces
As nagoya seems to down at the moment you can find the stylesheet
attached. 2 minor issues does it have:
- the old problem of namespace clean up. It copies all namespace
declarations from input to output, so also the old woody one's. Instead
of using xsl:copy I could have used xsl:element, but you need to
define then all needed namespaces in the stylesheet additionally
starting with i18n, maybe xhtml and so on. I prefer the post-processing
(removing the superflouos woody namespaces) over the pre-processing of
the stylesheet as adding additional namespace declarations is more error
prone than removing the old ones.
- whitespace-only text nodes (other must not be there) between comment
nodes are removed when they occur outside the root element. That's a
problem of Xalan. Inside the root element those text nodes are copied to
the output too. I saw this for form1-bind-bean.xml.
Joerg
?xml version=1.0 encoding=UTF-8?
xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:fb=http://apache.org/cocoon/forms/1.0#binding;
xmlns:fd=http://apache.org/cocoon/forms/1.0#definition;
xmlns:fi=http://apache.org/cocoon/forms/1.0#instance;
xmlns:ft=http://apache.org/cocoon/forms/1.0#template;
xmlns:wb=http://apache.org/cocoon/woody/binding/1.0;
xmlns:wd=http://apache.org/cocoon/woody/definition/1.0;
xmlns:wi=http://apache.org/cocoon/woody/instance/1.0;
xmlns:wt=http://apache.org/cocoon/woody/template/1.0;
xsl:template match=node()|@*
xsl:copy
xsl:apply-templates select=node()|@*/
/xsl:copy
/xsl:template
xsl:template match=wb:*
xsl:element name=fb:{local-name()}
xsl:apply-templates select=node()|@*/
/xsl:element
/xsl:template
xsl:template match=wd:*
xsl:element name=fd:{local-name()}
xsl:apply-templates select=node()|@*/
/xsl:element
/xsl:template
xsl:template match=wi:*
xsl:element name=fi:{local-name()}
xsl:apply-templates select=node()|@*/
/xsl:element
/xsl:template
xsl:template match=wt:*
xsl:element name=ft:{local-name()}
xsl:apply-templates select=node()|@*/
/xsl:element
/xsl:template
/xsl:stylesheet
Re: Status on Woody--CocoonForms renaming
On 07.03.2004 17:43, Joerg Heinicke wrote: As nagoya seems to down at the moment Seemed to be a temporary issue with the ISP, other sites did neither work. Closing and reopening a connection helped. Joerg
Re: Status on Woody--CocoonForms renaming
On Sun, 2004-03-07 at 17:43, Joerg Heinicke wrote: On 06.03.2004 19:09, Reinhard Pötz wrote: The first part is done - which means: - renaming of all Java classes - reflect changes within Flowscripts - first run on updating all samples open - Stylesheet for namespace change and change the namespaces As nagoya seems to down at the moment you can find the stylesheet attached. 2 minor issues does it have: - the old problem of namespace clean up. It copies all namespace declarations from input to output, so also the old woody one's. Instead of using xsl:copy I could have used xsl:element, but you need to define then all needed namespaces in the stylesheet additionally starting with i18n, maybe xhtml and so on. I prefer the post-processing (removing the superflouos woody namespaces) over the pre-processing of the stylesheet as adding additional namespace declarations is more error prone than removing the old ones. - whitespace-only text nodes (other must not be there) between comment nodes are removed when they occur outside the root element. That's a problem of Xalan. Inside the root element those text nodes are copied to the output too. I saw this for form1-bind-bean.xml. Wouldn't a simple text based search-and-replace be simpler then an XSLT? -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
Status on Woody--CocoonForms renaming (was: Update CocoonForms flowscript API)
Christopher Oliver wrote: Can we also get rid of the original Woody flowscript API as part of this process (and replace it with the v2 version)? The original was clearly not ready for prime time. -- Chris The first part is done - which means: - renaming of all Java classes - reflect changes within Flowscripts - first run on updating all samples open - Stylesheet for namespace change and change the namespaces - tidy up samples (get rid of first flowscript implementation, make them easier to understand, ...) - woody is used at many places (javadocs, parameter names, client-side javascript) -- as I want to learn more about CocoonForms I'll use this opportunity and go through all classes and make the updates. Expect the new block on Wednesday evening (GMT) ;-) as my time the next three days is very limited. -- Reinhard
Re: Status of Woody?
Timothy Larson wrote: What is the current status of Woody? status is still alfa (as in 'getting there') it should be usable for smaller short-lived projects here and now (gets the job done) but that usage is bound to generate more clues on typical usage that could guide us through essesntial refactorings in short: the code is probably more stable then the interfaces to it :-) I am running the nightly snapshot from 19-Aug-2003 03:17. http://cvs.apache.org/snapshots/cocoon-2.1/cocoon-2.1_20030819101653.tar.gz Several of the samples do not work: Various -- adds blank rows to Firstname Lastname... table at the bottom. I'm running cvs head and didn't see this (the firstname should be filled in) XML Binding -- Cannot add or remove contacts just tested this and saw the same, looks like a problem with the formhandler, I'll need a deeper look (but short on time here and now) Bean Binding -- Cannot add or remove contacts didn't test, but is using the same formhandler, so kinda logic Uh, 2nd thought: not logic at all: the Various sample is using the same FormHandler and it works over there! So this is actually tied to how the flow is dealing with the formhandler! (that's a part I haven't looked into) I know development is ongoing. Are these samples just not updated yet to match the code changes, or am I encountering Woody errors? probably a small Woody error in how it is tied up to the FlowScript... (need to check for updates in cvs there) regards, -marc= PS: Bruno is on holiday this week... -- Marc Portierhttp://outerthought.org/ Outerthought - Open Source, Java XML Competence Support Center Read my weblog at http://radio.weblogs.com/0116284/ [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Status of Woody?
Timothy Larson wrote:
What is the current status of Woody?
I am running the nightly snapshot from 19-Aug-2003 03:17.
http://cvs.apache.org/snapshots/cocoon-2.1/cocoon-2.1_20030819101653.tar.gz
Several of the samples do not work:
Various -- adds blank rows to Firstname Lastname... table at the bottom.
XML Binding -- Cannot add or remove contacts
Bean Binding -- Cannot add or remove contacts
I know development is ongoing. Are these samples just not updated yet to
match the code changes, or am I encountering Woody errors?
There has be no code change that should have intentionally broken
these samples.
This means we have to investigate and fix the bug ;-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
Status of Woody?
What is the current status of Woody? I am running the nightly snapshot from 19-Aug-2003 03:17. http://cvs.apache.org/snapshots/cocoon-2.1/cocoon-2.1_20030819101653.tar.gz Several of the samples do not work: Various -- adds blank rows to Firstname Lastname... table at the bottom. XML Binding -- Cannot add or remove contacts Bean Binding -- Cannot add or remove contacts I know development is ongoing. Are these samples just not updated yet to match the code changes, or am I encountering Woody errors? --Tim Larson __ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
