You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
XML Schema supports the <choice> construct. YAWL has rendering and handling
errors of these in the following cases:
-- for *any* choice field (e.g. a choice between two simple string
elements, as in the attached log extract), choosing anything other than the
first option causes empty XML elements to be produced for the other choices
as well. This causes a schema validation error since there should only be
one choice alternative
-- for *complex type* choice fields (e.g. sequences of two strings, as in
the attached log extract), they are rendered without their parent element
name (see attached screenshots) and, when choosing one, the parent element
is missed off, giving schema validation errors again
-- choices within a sequence erroneously get rendered/handled as multiple
instances. In the example in the screenshot and log extract, a sequence is
defined with a single choice of two elements inside. This is rendered as
*two* instances of the choice elements (and there are no +/- icons to
remove them). My guess is that the code is counting the number of elements
in the sequence without handling the existence of choice parent tags
What steps will reproduce the problem?
1. Create any "blank" project with schema definitions for choices as
indicated (see log details which have the full DTD listings in)
2. Start the case and observe the rendering issues (where relevant)
3. Enter some starting data and observe the incorrect XML produced in the
logs (DEBUG level)
What is the expected output? What do you see instead?
See above
What version of the product are you using? On what operating system?
2.0 Final on Ubuntu Jaunty
Please provide any additional information below.
The case numbers in the screenshot names refer to the cases in the
annotated log file extract
Original issue reported on code.google.com by [email protected] on 15 Oct 2009 at 4:12
Original issue reported on code.google.com by
[email protected]
on 15 Oct 2009 at 4:12Attachments:
The text was updated successfully, but these errors were encountered: