>fix them upstream then ship a forked copy until a new Android >release re-merges, or use a different dom implementation.
seems i'm up against it here too. i included a copy of the harmony DOM source in my Android project, and it builds fine, but at runtime it uses the regular one. is there a way to force the usage of the local one? i'd use another DOM, but Xerces won't let me instantiate its document implementation directly, so i'd have to change the parser factories in javax.xml.parser. i'd be up for doing that, but Android heads me off at the pass there too by not allowing me to include anything off java.* or javax.* in my apk. it would be really nice if the javax.xml.parser.* factories could be configured to make Documents from different implementations, but i'm not seeing how right now. thanks in advance, -- jason.software.particle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
