Chaotic Java

After not touching the yielder project for a long time, I decided to go back and make the change I knew I needed but feared of doing: changing from the visitor model to the tree model of ASM.

It wasn’t even about performance anymore, as I was sure that the performance would be just as great. It was about needing to rethink the entire model again, and about being lazy.

Laziness is the end of all home-made projects, indeed.

Enough rants. I made the change, and now all the problems the previous version used to have – such as methods not necessarily working in a yield clause etc, are working.

Please, read all about it here, and get it from the Google Code project here. And obviously, let me know how it works for you, either in comments or on the issues page, here.

Thanks!

For those of you who don’t know what OpenID is, get to know it now. This post is going to be about how to use OpenID authentication in your GWT applications.

First, a reminder of what OpenID is:

OpenID is a free and easy way to use a single digital identity across the Internet.

Continue reading »

Functors are defined as a function encapsulated in an object. In most cases, the function’s parameters can be set and the result retrieved using the common accessor pattern, such as setParameter1(Object value) or getResult(). The fact that these functions are encapsulated by real objects is also the reason for its greatest benefit: the use of many design patterns including structural ones such as the Decorator pattern and behavioral ones such as the Visitor pattern.

Functors in software design

While the classic object oriented design encourages inheritance and method overloading to achieve code reuse and code specialization, the functors’ design promote another approach, of composition. Functors are created to accomplish simple tasks and are later connected together, by connecting one functor’s result to another’s parameter, to satisfy a greater goal of the application.

Continue reading »