X

Geertjan's Blog

  • September 18, 2008

Groovy Web Services and org.apache.cxf.endpoint.dynamic.DynamicClientFactory

Geertjan Wielenga
Product Manager
The title of this blog entry is meaningless... except... if you want to use Groovy Web Services with JDK 6.x (instead of JDK 5.x). I wrote about the embarrassingly easy web services in Groovy before and then today ran into the error that starts with this line:

org.apache.cxf.endpoint.dynamic.DynamicClientFactory outputDebug

Yes, it is an illuminating start to a long stack trace, isn't it? (That's why I put it in the title of this blog entry, hoping to draw frustrated Googlers here, so they can see for themselves what the solution is.) So here's hoping that Google will bring you to this blog entry, because (good news!) ALL YOU NEED TO DO IS PUT JAVA_HOME/BIN ON THE CLASSPATH! (Read more here which is where I found this tip.) IntelliJ people might also benefit from this knowledge, as evidenced here:

http://www.jetbrains.net/jira/browse/GRVY-889

So, to reiterate, in JDK 6.x, you need JAVA_HOME/bin on the classpath (not just JAVA_HOME, as was the case with JDK 5.x), otherwise you'll get a nightmarish stack trace instead of your wonderful web service payload retrieved from the web.

Join the discussion

Comments ( 2 )
  • anjan bacchu Thursday, September 18, 2008

    hi there,

    easy web services in groovy : refers to web service client or server ?

    I never put JAVA_HOME or its bin in the PATH. So, what kind of classes are inside the BIN directory in java 6 ?

    Thank you,

    BR,

    ~A


  • Bertrand Goetzmann Tuesday, September 30, 2008

    Hello Geertjan,

    I get a similar error when trying to call a Java web service deployed on Glassfish from a Groovy client using GroovyWS 0.3.1.

    You can have a look to the Romen's post about "Consuming WCF Web Service Using Groovy Client" (http://romenlaw.blogspot.com/2008/08/consuming-wcf-web-service-using-groovy.html), in witch Romen takls about a bug on CFX bundled which GroovyWS, and its solution.

    Cheers,

    Bertrand


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.