Grails

ant tomcat deploy task hangs

I tried to use the catalina ant tasks  to deploy my grails war into tomcat, and it's not working well in hudson.  So, I am just going to do the tried and true method.

/root/local/jakarta-tomcat/jakarta-tomcat-5.0.28-8080/bin/shutdown.sh

Hudson continuous integration server with grails

I was up until 2 am last night setting up the stitches project with hudson.  I am NOT complaining.  I had to configure a few projects to build/test and DEPLOY into the demo tomcat instance.
http://demo.philliprhodes.com/hudson/

Using wicket in a grails app

I am a HUGE fan of wicket.  Amazing how productive and awesome it is.  Anyway, I was developing a grails application as an example client to the stitches repository.  Ouch, which everything works, it's so tedious.  Loop here, fetch her, set this, get this.  Down to the nuts-n-bolts of an action-oriented framework.

Ivy in grails

I've been a maven boy for a while.  It's not the best thing in the world, but it beats maintaining with hundreds of lines of ant build files.  In grails, I missed maven, but I see there is a ivy plugin.  I bit the bullet.

In order to use Ivy for dependency resolution, you need to install the ivy plugin:

grails install-plugin ivy

After you do this, you can now run "grails get-dependencies" and ivy will dump all your jars into your applications lib directory.

State of WS clients in Grails 1.1

The following is just a posting from a few days of digging.   Hopefully it can help others.  I am not a WS expert at all, just a developer trying to get a client to work, that said, if everything is mis-stated below, please correct me.

> javax.xml.stream.FactoryConfigurationError: Provider > com.bea.xml.stream.MXParserFactory not found

I got this error, so of course, I looked around for this jar.  Couldn't find any.  Then I just did a dump from the xfire/lib distribution direction into my project, and the error went away.

Jar Hell in Grails

Got me tests working, and tomcat is finally running my application.
However, now grails jetty will not start.

groovy can't handle the output of wsdl2java

Oh, up until 1 am last night with this issue.

I ran a wsdl2java against the stitches webservice and have a nice suite of classes that I can use to connect o stitches.  i created a groovy class to instantiate the client, and it WILL NOT compile.

Turns out the the wsdl2java generated a lowercase classtype "stitches" which is an interface.

Hence, while this would compile in java, it does not compile in groovy

stitches mystitches = null

Posted the issue on the groovy list...  Hopefully someone will at least give me an idea of how to proceed.

groovyws, too much of a good thing is bad;)

stitches, my grails-based project has an example client that uses the groovyws to connect to the soap services that stitches exposes.  I have tests that invoke, "push, pull, prod" the web services to do all kinds of things.   However, on a very regular basis, I was getting the following perplexing error:

 

 

Grails runs bootstrap for integration tests tripped me up

I stayed up a little too late last night trying to get my grails tests to complete.  I didn't want to give up.

Syndicate content