I'd open an issue at that prototype component instead - a json object is an unordered collection of key/value pairs. If order is important, they should be using arrays. AFAIK, at least in Chrome and Opera the iteration order is not guaranted to be the same as the insertion order.
On Mon, Sep 13, 2010 at 17:28, Michael Dukaczewski <m.dukaczew...@tu-bs.de> wrote: > Hi! > > I have a problem with the JSONObject in Tapestry. I would like to use a > Javascript Prototype component which expects a JSON object. The > component outputs the data in the order they were transmitted in the > JSON object. The problem is that in the implementation of the JSONObject > in Tapestry a map is used and therefore the order is lost. Here, an > OrderedMap would be the better choose. Should I open a JIRA on this? > > Regards, > Michael > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
