As said by DP,
I had to add the following to my pom.cml to make it work
dependency
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
version2.11.0/version
/dependency
dependency
groupIdxml-apis/groupId
artifactIdxml-apis/artifactId
I had similar problem. I resolved it by adding xercesImpl artifact to my
Maven pom.xml
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi,
Did you see more in stack trace beyond line 81 ? There must be some
thing Caused by.
= Abstract method error - as per javadoc
Thrown when an application tries to call an abstract method
Yes this incompatibility between jars and some time jvm or simply non
implemented abstract method
I
Hi all,
thank you for your hints. I throw out the EAR-Lib path from the project's
classpath (where JBoss' XercesImpl.jar was in) and now I'm down to a
different error.
My current problem is that the GWT compiler started from the Google Eclipse
Plugin seems to use the project's classpath. Now in
Hi all,
we have a GWT project which is suddenly not compiling anymore but
failing with an INternal Compiler error at
com.google.gwt.uibinder.rebind.W3cDocumentBuilder.startElement(W3cDocumentBuilder.java:
128).
This happens since a collegue of mine has made some changes
(unfortunately he's two
I think is a classpath issue. You have more than a SAX Parser in your
classpath and this is the problem. I have a similar problem and resolve (in
maven, not in eclipse). See this
threadhttp://groups.google.com/group/google-web-toolkit/browse_thread/thread/4645c2e495492306
2011/7/14 Jörn Gersdorf
