Share a link to this question via email, Google+, Twitter, or Facebook. This workaround allows me to continue to use Groovy 1.0 (and hence the eclipse plugin) so as far as I'm concerned the issue is closed, but I will leave it open asked 4 years ago viewed 3329 times active 4 years ago Upcoming Events 2016 Community Moderator Election ends Nov 22 Related 0MissingPropertyException while running unit tests for Grails service class0groovy Command Show Matt Kennedy added a comment - 19/Sep/07 10:00 Thanks for the guidance on this, for others that might read this, here is what eventually solved the issue: As per Jochen's have a peek at this web-site
Maybe a classloading order problem...: runtime group: 'org.grails.plugins', name: 'hibernate4', version: '18.104.22.168' OS: Windows 7 x64 Java: build 1.7.0_60-b19 Gradle: 1.12 Grails-Gradle-Plugin: 2.0.1 Grails: 2.4.0 Successfully started process 'command 'C:\Program Files\Java\jdk1.7.0_60\bin\java.exe'' Obviously, every application is different, and there are also good reasons for putting libraries in the lib directory, not least the fact that they're needed by the application! asked 2 years ago viewed 333 times Upcoming Events 2016 Community Moderator Election ends Nov 22 Related 0groovysh and groovy classes visibility and annotation parsing4How to add imports to groovysh on SystemAdmin 110000D4XK 590 Posts Re: SAX parser and classloader 2011-10-10T14:44:25Z This is the accepted answer.
My application use spring 2.5 and a lot of jar files activation-1.1.jar jdom-1.0.jar antlr-2.7.7.jar jstl-1.1.2.jar aopalliance-1.0.jar junit-3.8.1.jar asm-2.2.3.jar log4j-1.2.12.jar asm-all-2.2.3.jar mail-1.4.jar axiom-api-1.2.2.jar neethi-2.0.4.jar axiom-dom-1.2.2.jar opensaml-1.1.jar axiom-impl-1.2.2.jar oro-2.0.8.jar axis2-1.1.jar poi-2.5.1-final-20040804.jar bcprov-jdk15-140.jar saaj-api-1.3.jar I removed xml-apis-1.0.b2.jar and problem is resolved. Share a link to this question via email, Google+, Twitter, or Facebook. Because they're OSGi-based, WABs are fully modular, so all of the binaries in the lib directory can be eliminated and instead expressed as a slim little declarative dependencies.
Regards, Alex. For example if you add xmlParserAPIs jar (from say Xerces 2.x.x distribution) and NOT add the xercesImpl jar itself. Research Specialist > Metabolomics Fiehn Lab > UCD Genome Center > 451 East Health Science Drive > GBSF Building > University of California > DAVIS > 95616 > http://fiehnlab.ucdavis.edu/staff/haldiya/> -- ------------------------------------------------------------ Provider Org.apache.xerces.jaxp.saxparserfactoryimpl Not Found The cause for the duplication is the way RootLoader works...
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed LeeGDavis commented Jun 13, 2014 Confirmed! Show Matt Kennedy added a comment - 20/Sep/07 17:08 I'm reopening this issue in hopes of finding a workaround that will let me continue using Groovy 1.0. What do I do with my leftover cash?
Again, what jars are needed will vary depending on what application server is being used, but the more full-featured the application server, the fewer libraries the application needs to haul around Maven Xerces No exact cause was identified since upgrading to Grails 1.3.2 resolved this problem, while introducing a few other dependency issues. –Ruben Jun 23 '10 at 11:29 add a comment| active oldest More... Hide Permalink Jochen Theodorou added a comment - 20/Sep/07 18:46 sorry, I have a small problem in understanding...
What's the risk of leaving VPP/MCLR floating? The result is the ClassCastException. Provider For Javax.xml.parsers.documentbuilderfactory Cannot Be Found Websphere At the risk of sounding like a proud developer (sort of like a proud parent, but with more code involved!), one of the things that we think is great about the Provider For Javax.xml.parsers.saxparserfactory Cannot Be Found don't need to republish the whole EAR. -Joel Show: 10 25 50 100 items per page Previous Next Feed for this topic
I think that will solve your problem Show Jochen Theodorou added a comment - 18/Sep/07 20:09 could you please try to remove the xerxes and xalan jars from the lib directory http://urldt.com/cannot-be/import-javax-servlet-servletexception-cannot-be-resolved.html Feel free to close it if you don't. fdut 1100009M9S 2011-10-10T15:01:13Z thanks for your help. Reload to refresh your session. Provider Org.apache.xerces.jaxp.saxparserfactoryimpl Not A Subtype
Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Would we find alien music meaningful? Is there an extra step required to get the jaxp debugging statements from a grails command line? Source Join us to help others who have the same bug.
Show Jochen Theodorou added a comment - 20/Sep/07 18:46 sorry, I have a small problem in understanding... So I removed it and it worked again. In a world with time travel, could one change the present by changing the future? Browse other questions tagged groovy groovyshell or ask your own question.
Well maybe we need more virtual servers and more clusters. Below is a quick addition to the script I posted originally that seems to show that the workaround provided (removing xerces and xalan) will allow java.util.Preferences objects to work with XML, Why do languages require parenthesis around expressions when used with "if" and "while"? have a peek here Teenage daughter refusing to go to school Does my electronic parking brake remain engaged if I disconnect the battery?