Lambda support is planned for JDK 8. The process I used was to build the patched compiler from langtools repository (bleeding edge) that supports Lambda expressions. It was outlined in my original entry, in case if you missed it. JDK 8 dev builds are starting to appear here, unfortunately it does not yet support lambda expressions. I am hoping that day is not too far.

-Arul

You certainly make a good point about maintainability of code. I believe Kotlin and Ceylon has similar intentions to keep learning curve as minimal as possible and still be productive with expressiveness of the language without compromising simplicity.

It is true the gap is widening between C# and Java in terms of innovation, which can only be compensated by these noble attempts in the JVM ecosystem. I wish they make the prototype compiler available soon, wanting to try out some of these cool features.

Thanks,
Arul

Well, at least from this recent InfoWorld article, it looks like IDEA is topping the Java IDE category. Any way, the point is not about IDEs here, JetBrains obviously has commercial interest in producing a competitive language (which btw would be Apache licensed) backed by a quality IDE. It looks like Eclipse already has Xtend, which probably has similar intentions but not full blown language like Kotlin or Ceylon.

Thanks,
Arul

Umm, last time I checked, the leading Java IDE maker is Eclipse. What is the Kotlin story for Eclipse?

One thing is certain: all of this “exploration” in the space of language design will yield a _better_ net result. I have had feature envy over C# for years, but think that when this NBJL phase completes we’ll end up with something _more_ expressive with _less_ cognitive cost — i.e. “better”. Just as Java’s middleware ecosystem is better via competition and “community exploration” so too will its language (I hope).

Steve

No problem!

I was actually referring to using “==” in the URI as shown below.

WebClient wc = WebClient.create("http://localhost:9000/sakila/searchActors?_s=firstname==PENELOPE");

This would return a 404, but if I encode “==” as shown below, it works just fine.

WebClient wc = WebClient.create("http://localhost:9000/sakila/searchActors?_s=firstname%3D%3DPENELOPE");

It can also be reproduced when using other operators in search query such as “!=”.

I am not certain if this is the correct way to construct WebClient instance which takes the baseUri including query parameters. I believe another option is to use it as shown below, which works fine.

WebClient wc = WebClient.create("http://localhost:9000/sakila/searchActors");
wc.query("_s", "firstname==PENELOPE");

Btw, thanks for implementing such an useful feature in CXF JAX-RS.

-Arul

Can you please let me know which operators you had to encode explicitly for WebClient to work ?
thanks for a great post
Sergey