| 526 | | be replaced when the schema is updated." |
| | 526 | be replaced when the schema is updated."[[BR]] |
| | 527 | [[BR]] |
| | 528 | ''Stephanie:'' If indeed, the issue lies with the plural forms of complexType names (used for lists of resources) in the schema, we think that, principally, the plural forms can - and should - be replaced more or less immediately, e.g. by adding the suffix "{{{List}}}" or "{{{Collection}}}" instead of plural "s". For instance, the serialized xml output could then match the following snippet |
| | 529 | {{{ |
| | 530 | <annotationCollection> |
| | 531 | <annotations> |
| | 532 | <annotation> |
| | 533 | <!-- elements of annotation --> |
| | 534 | </annotation> |
| | 535 | </annotations> |
| | 536 | </annotationCollection> |
| | 537 | }}} |
| | 538 | |
| | 539 | By the way, speaking of diverse "JAXB plural issues", there were some hints on the web regarding (inline and external) Java binding customization for JAXB, - it might be that this would also be a viable solution approach. Maybe this thread is worth checking as well: http://stackoverflow.com/questions/11943487/please-advise-the-best-pattern-for-serialising-jaxb-lists? |
| | 540 | |
| | 541 | As regards all future schema updates, please make sure to remember to update all available scenario xml documents on trac.clarin.eu accordingly, and preferably, with as little delay as possible. It might also be a good idea to validate all of these documents against the revised schema with a reliable XML parser like e.g. the Xerces-J XML parser. Also, if you like, you can check by validating some of our current "real-life" mock xml documents that we have been using recently for client development ([source:DASISH/t5.6/client/trunk/chrome/markingcollection/content/markingcollection/annotator-service/test/mockjax/mocks]). |
