Closed GoogleCodeExporter closed 9 years ago
This will be needed for being on par with our old APIs as well.
Original comment by anli.shu...@gmail.com
on 15 Oct 2012 at 2:53
and Foreign Namespace Attributes need to preserve the namespace context to
resolve possible QNames in values
Original comment by anli.shu...@gmail.com
on 15 Oct 2012 at 2:54
Patch submitted by Yury to the mailing list, with some updates and discussion
that occurred offline, to get clarity. This is going to be completed in stages,
though: api + bridgekit first, then modifications to the processor.
Also note that while there is a TODO noting the need for QName-in-content
support, we're not doing that to start with (QNames in content are *evil*).
Original comment by aale...@gmail.com
on 25 Oct 2012 at 8:17
Most of the work for this has been done by r411. api and bridgekit changes were
committed in r404. r405 to r409 involved cleaning up the mess in the parser
impl, which included renaming the xmlrep schema model (a more lexical model
than the api model) in a way that allows it to be exported (no "impl" particle
in the package name), together with ruthless reorganization of the parser
(though I didn't touch the exceptions, which are an abomination in the sight of
Gosling).
At this point, the schema parser preserves foreign attributes, passing them to
the xmlrep model. The API/bridgekit model exposes foreign attributes. However,
I have not connected the pieces (XMLSchemaConverter doesn't copy the attributes
from xmlrep to api model, yet).
Original comment by aale...@gmail.com
on 26 Oct 2012 at 7:42
This issue was closed by revision r412.
Original comment by aale...@gmail.com
on 29 Oct 2012 at 5:05
Original issue reported on code.google.com by
yury.ska...@gmail.com
on 15 Oct 2012 at 2:38