cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12986] New: - XMLForms: Form class locate() loses order of nodes in returned Set
Date Wed, 25 Sep 2002 05:45:43 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12986>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12986

XMLForms: Form class locate() loses order of nodes in returned Set

           Summary: XMLForms: Form class locate() loses order of nodes in
                    returned Set
           Product: Cocoon 2
           Version: Current CVS
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: general components
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: samc@atnet.net.au


public Set Form.locate(String xpathSelector) :
after obtaining an iterator for the child nodes selected, the iterator is 
walked in order to place the items into a HashSet, which does not guarantee 
that the iterator obtained from it will preserve the order of items in 
insertion-order.

This causes the XMLFormTransformer to incorrectly transform the model, putting 
items out of order. This does not happen when less than 10 items are resolved 
by the XPath, most likely due to the memory allocation semantics of HashSet. 

If you create a model and a form which uses the repeat construct over 10 or 
more items, you can see how the form model will get incorrectly transformed.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message