The change was that I turned on XML validation. The order is constrained, but doesn't necessarily have to be, if people think it shouldn't be... I've made some of the sub-elements not choosy about the order of their sub-elements because it was a pain....
Jason > -----Original Message----- > From: Jonas Eriksson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 6:15 AM > To: [EMAIL PROTECTED] > Subject: [OS-webwork] Order of elements in xwork.xml > > > Hi! > > I recently updated my version of ww2 and it all stopped working (what > was I expecting... ;-) > Somehow my xwork.xml was not accepted by the configuration parser: > > org.xml.sax.SAXParseException: The content of element type "package" > must match > "(result-types?,interceptors?,default-interceptor-ref?,global- > results?,action*)". > at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) > > The problem was that the order of these elements was not the > same as in > the error message above. Is this how it should be? (I don't know very > much about xml and parsing but it seems pretty stupid if the > order of, > not related, elements is constrained) > > /Jonas > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
