diff options
author | Jeff Sharkey <jsharkey@android.com> | 2020-11-18 16:20:48 -0700 |
---|---|---|
committer | Jeff Sharkey <jsharkey@android.com> | 2020-11-30 20:45:25 -0700 |
commit | 42bd76058f1ba49f5befd5412f205f153d3ff3c3 (patch) | |
tree | e0c6b7c2a4280a0b1bf29db7ffd7432ab8dcc340 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
parent | a01f750588e7016461d400671fdfaa2f91fde990 (diff) |
"Resolve" both human-readable and binary XML.
Recent refactorings have pivoted many XML users across the system
to call resolveSerializer() and resolvePullParser(), which gives us
an easy path to pivot between human-readable XML and our binary XML
wire format.
This change introduces a feature flag (still disabled by default)
for emitting binary XML by default when serializing. It also adds
logic to automatically select the relevant parser by sniffing the
magic file header.
This is the key to our upgrade strategy: we'll gladly parse
human-readable XML from old devices, or binary XML from new devices.
Bug: 171832118
Test: atest FrameworksCoreTests:android.util.XmlTest
Test: atest FrameworksCoreTests:android.util.BinaryXmlTest
Change-Id: I14fdab9a6667819db38116a8ce126f5f2a5a04df
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions