> Mark Murphy wrote: > If you are including xml-apis in your build, that might conflict with > existing DOM and SAX implementations in Android. Try removing xml-apis > from the build and see what happens.
removing xml-apis from the build path results in errors in a few scxml classes. One of which is SCXMLSerializer, I think i could spare this since the Serializer is only called from some test classes. More tricky is that it also breaks Builtin.java which is a central class within scxml. The only class needed from xml-apis is the javax.xml.transform.TransformerException The TransformerException is thrown by org.apache.xpath.XPathAPI which itself is part of xalan, which i still have in the build path. But wouldn't that mean that the hole of xalan is incompatible to android? Or the other way around, if xalan works on android it would mean that its inside use of java.xml.* succeeds. And that hence i could find a way making it work for me as well. Is there anyone who used xalan on android? On 24 Sep., 16:14, Mark Murphy <[EMAIL PROTECTED]> wrote: > Jakob Sachse wrote: > > Mark Murphy wrote: > >> If that does not clear up your problem, you can try merging the > >> commons.scxml source into your own project's source tree > > > well, basicly thats what i have done so far > > Oh. Sorry, missed that. > > > though, i will try to build the jar as you recommended. Even if the > > problem, as far as i see it > > comes mainly from the javax.xml package which seems to collide with > > the Android SDK in some way. > > Do you have all the source code to all the commons-scxml dependencies? > > If not -- meaning you have commons-scxml source but are still using > third-party JARs -- start trying to introduce those, either fully into > your project, or simply recompiling them using your own Java compiler. > Or, get rid of dependencies that may collide with what is in the Android > SDK/ > > For example, according to the dependency chart: > > http://commons.apache.org/scxml/dependencies.html > > commons-scxml depends upon Xalan, which depends upon xml-apis. > > If you are including xml-apis in your build, that might conflict with > existing DOM and SAX implementations in Android. Try removing xml-apis > from the build and see what happens. > > -- > Mark Murphy (a Commons Guy)http://commonsware.com > _The Busy Coder's Guide to Android Development_ Version 1.2 Published! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
