Paul Bakker - All Comments

re: Testing Grails REST services

Steve Dalton — Mon, 30 Nov 2009 22:48:48 GMT

Thanks Paul

The controller.response.getContentAsString bit was just what I was looking for.

Steve

re: Open source, free Community Edition of IntelliJ

Ryur — Fri, 16 Oct 2009 06:58:47 GMT

Nice. I'm going to try it.

I'm now an Eclipse-user, but it is sometimes so slow, even on a new MacBookPro.

re: JavaFx Charts

Paulb — Fri, 25 Sep 2009 09:18:25 GMT

Fernando,

You should just use a Java library for this. That's one of the advantages of JavaFX, you can use existing Java code/libraries. It's best to only write your UI code in JavaFX, the language is not intended to be a all purpose language like Java.

re: JavaFx Charts

Erno de Weerd — Fri, 25 Sep 2009 04:30:13 GMT

FC,

As someone with a C background:

What's with the End everywhere:

If ... Then

Else

End If

Sub ...

...

End Sub

And why do I HAVE to put the If and the Then on a single line?

What's the Then good for anyway?

In Java (and C/C++/C#/...) we have free formatting; we can put nearly anything on any line so we need a way to tell the compiler when we have reached the start and the end of a statement. and { ... } is waaaayyyy shorter than Begin ... End

re: JavaFx Charts

Fernando Cassia — Thu, 24 Sep 2009 05:03:27 GMT

Totally unrelated question.... is there support in JavaFX for common protocols like POP3 and IMAP?. Any standard classes I can call?.

I'd need to fetch data (not the actual emails but sender info and subject lines) from an IMAP account.

Thoughts? Comments? Expletives?

Best,

re: JavaFx Charts

Fernando Cassia — Thu, 24 Sep 2009 05:00:34 GMT

As someone whom comes with a Visual Basic background, you know what drives me crazy?

The damn

{

bracket chars

}

everywhere.

And why do bracket chars need to be on a single line?

Why

{

this

}

Instead of {this}

re: Testing Grails REST services

Stephane — Sat, 19 Sep 2009 13:35:56 GMT

It'd be nice if the example showed how to unit test this RESTful GET request for example:

curl --request GET --header "Content-Type: text/xml" localhost/.../1

re: log4j in Websphere Portal Server 5.1

Sean — Fri, 21 Aug 2009 21:30:26 GMT

checkout my post, it will solve your problem.

mycrappytechnologyblog.wordpress.com/.../websphere-portal-log4j-hell

re: Testing Grails REST services

Just one punctuation mark this time. - Nick — Fri, 21 Aug 2009 14:39:52 GMT

Paul,

Sorry to come across snarly in the first post.

Thank you for your example. How to test sending / expecting different formats will come in helpful when testing my controllers (RESTful or not).

The point I was trying to make was that the article is titled "Testing Grails REST services", but does nothing as far as testing anything RESTful. When people are trying to learn about RESTful services, and they come across an article like this, they will believe that all a RESTful service means is that it can do some sort of content negotiation.

I just had a lost feeling after reading, and felt a buzzword was used to get attention to the article. There is far to much of that out here.

But again, thank you, and sorry again for the first post coming across like that, should have probably waited to post or not posted anything at all.

-- Nick

re: Testing Grails REST services

gphreak — Fri, 21 Aug 2009 12:51:42 GMT

I wonder why people using punctuation marks in large packs always end up to be idiots.

Nice example, Paul, thanks.

re: Testing Grails REST services

Paulb — Thu, 20 Aug 2009 20:33:09 GMT

It's a simplified example. The example controller is not a REST service, it just returns XML, but a full blown service can be tested the same way. It would just be more code.

re: Testing Grails REST services

where is the REST???? — Thu, 20 Aug 2009 19:09:01 GMT

So...this is really on how to send a format to a controller in a test...not really how to test a REST service???

JavaFX 1.2 Folder Visualizer

Paul Bakker — Tue, 18 Aug 2009 08:37:46 GMT

Last year I blogged about a small JavaFX project I implemented called Folder-Visualizer. The tool lets

re: Why not Groovy all the time?

Paulb — Mon, 03 Aug 2009 21:37:57 GMT

Good question. I don't have much problems debugging Groovy. There is often some extra clutter in stacktraces compared to Java, but most of the time it's still easy to find where the code you wrote is broken. I do use Intellij for all Groovy stuff, which gives me clickable stacktraces, making it more easy to find the interesting information in a stacktrace.

What I do find however, is that I sometimes introduce bugs by making simple typos. In Java the compiler stops you from doing this, but in Groovy it doesn't. If you're lucky (most cases) the errors shows up as soon as you try to start the app, but it introduced some minor bugs that I overlooked too. This can be solved by better unit testing, which is easier in Groovy. A good IDE helps too, but isn't always enough because the dynamic nature of Groovy. Using more static typing helps too, but defeats the purpuse of using a dynamic language... ;-)

I still do feel it's a major drawback compared to static typed languages. That being said, I would still choose Groovy for most code at the moment.

re: Why not Groovy all the time?

Jeremy Flowers — Mon, 03 Aug 2009 20:27:42 GMT

How easy do you find debugging Grovy compared to Java?

See:

www.troymaxventures.com/.../switch-your-test-to-groovy-maybe-not.html

Congrats on winning the Radrace contest with Jamie BTW