Skip to main content

Groovy beans

A typical Java Bean is a Java class which is serializable, has a public no-arg constructor, private attributes, and getter/setter methods. I'd say this is a lot of stuff for a simple pojo.

Groovy beans did to pojo's what Java could not. They are actually simple. A typical Groovy bean needs to implement java.io.Serializable and add properties to it. We do not need to add any getters/setters, they are added automatically for us.

Here is a simple Groovy bean.


class Customer implements java.io.Serializable {
String firstName //will be a private attribute in the bytecode
String lastName //will be a private attribute
def middleInitial //beans can even contain dynamic properties
}


See.... Groovy beans do not have any getters or setters, and you will also have noticed that the fields are not private. Even though the source does not contain getter/setter methods and private attributes, the bytecode does. When this bean is converted into bytecode all attributes which do not have an access modifier will be treated as properties. What this means is, they will become private attributes and public getter/setter methods will be generated for them.

Now let's create an instance of this bean.


def customer = new Customer()
//Even though this looks like we are accessing public fields
//the bytecode actually invokes the setter methods of these properties
customer.firstName = "John"
customer.lastName = "Gardner"
customer.middleInitial = "U"
println 'Customer's Last Name: ' + customer.lastName


Creating an instance of a Groovy bean is very similar to Java, but assigning values to it's properties seems to be a bit different. When we assign the value "John" to firstName, it seems as if we are assigning a value to a public field. But this is not what happens. Internally Groovy converts this into a call to the setter method for that field. Thus we get the same end result as in Java, but with less verbosity.

We can also use the bean constructor to instantiate and initialize the bean together.


def customer1 = new Customer(firstName: "Bob",
lastName: "Steele",
middleInitial: "Z")


In the above code this is what really happens under the hoods. First the constructor is invoked, followed by calls to the corresponding setter methods.

This is wonderful. Groovy Beans are just like Java Beans, but much simpler and smaller.

Now, you must be thinking, but what if I want to add custom code to the getter or setter? That is simple, simply create your own getter or setter and Groovy will use your code instead of automatically generating it's getter or setter. Your getter/setter can either be public or even protected if you so wish.

But what if we want to create a simple field without getters and setters. How do we prevent Groovy from automatically inserting getter/setters in the bytecode. Again simply create a field and give it an access modifier (like 'private') and Groovy will not auto generate anything for you.

One question that comes to mind, is how do we create package private attributes? Since Groovy 1.6, a package private field can be created by annotating it with @PackageScope

Comments

Unknown said…
hey it was a great information .
keep it up!!

Popular posts from this blog

Running your own one person company

Recently there was a post on PuneTech on mom's re-entering the IT work force after a break. Two of the biggest concerns mentioned were : Coping with vast advances (changes) in the IT landscape Balancing work and family responsibilities Since I have been running a one person company for a good amount of time, I suggested that as an option. In this post I will discuss various aspects of running a one person company. Advantages: You have full control of your time. You can choose to spend as much or as little time as you would like. There is also a good chance that you will be able to decide when you want to spend that time. You get to work on something that you enjoy doing. Tremendous work satisfaction. You have the option of working from home. Disadvantages: It can take a little while for the work to get set, so you may not be able to see revenues for some time. It takes a huge amount of discipline to work without a boss, and without deadlines. You will not get the benefits (insuran

Testing Groovy domain classes

If you are trying to test Grails domain class constraints by putting your unit test cases in the 'test/unit' directory, then your tests will fail because the domain objects will not have the 'valdate' method. This can be resolved in two ways: Place the test cases inside test/integration (which will slow things down) Use the method 'mockForConstraintsTests(Trail)' to create mock method in your domain class and continue writing your test cases in 'test/unit' What follows is some example code around this finding. I am working on a Groovy on Grails project for a website to help programmers keep up and refresh their skills. I started with some domain classes and then moved on to write some unit tests. When we create a Grails project using grails create-app , it creates several directories, one of which is a directory called 'test' for holding unit tests. This directory contains two directories, 'unit', and 'integration' for uni

Some thoughts on redesigning education

Some time back I read a blog post on redesigning education. It asked some very good questions. Stuff which I had been thinking of myself. I left my thoughts on the blog, but I would also like to start a conversation around these ideas with those who read this blog as well. I would like to know what other people think of the issue of redesigning (college) education. I have often thought about how college education can be improved. To answer this question, we first have to ask a very basic question. What is the purpose of education? To me, we need education for 3 things: To learn more about the world around us To lead positive constructive lives To earn a good living / fulfill our ambitions I think education has to a large extent evolved to fulfill #3 (with a bias towards earning a comfortable living). The semester system, along with multiple choice tests, and grading, has made our education system into an assembly line. Students are pushed into the assembly line, given classes, admini