--- "Matthew J. Graham" <[EMAIL PROTECTED]> wrote: > What is the timescale for fixing this bug? I really need it sorted out > by the end of the week and it is now the major showstopper in my > application as the instance documents generated are not valid - missing > elements. If you can point me at where the problem might lie in the > source code, I am happy to try and "fix" it.
This is not necessarily trivial. Right now when <xforms:itemset> is used, we unroll it into multiple <xforms:item> in the XFormsOutput processor. Then the rest of the code doesn't need to know about <xforms:itemset> and only handles <xforms:item>. Obviously this does not lead to the expected result when an element instead of a text node is referenced from <xforms:copy>. To correctly handle the <xforms:itemset>, in the current code: 1) The XFormsOutput processor must annotate the <xforms:value> with xxforms:node-ids="..." when unrolling the <xforms:itemset>. 2) The names generated in XFormsOutput must be changed: instead of having just "$node^", we should have "$value-to-node" (replaces "$node") and "$node-to-node". The later is used for <xforms:itemset>. 3) xforms-to-xhtml.xsl must handle the xxforms:node-ids attribute on <xforms:value> if present. 4) The XFormsInput processor (specifically RequestParameters.java) must handle "$value-to-node" (replaces "$node") and the new "$node-to-node" attributes. Again this is not trivial. At this point fixing this has not been scheduled yet, so I cannot give you an ETA for this bug. If you wish to sponsor this bug fix, please contact Omar directly ([EMAIL PROTECTED]). Alex ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
