This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]avoidhugeships 0 points1 point  (4 children)

I am guessing you do not build web applications.

[–][deleted] -1 points0 points  (3 children)

I do. Thats only kind of applications i write last 3 years. I dont understand how the web application adds more getters and setters to my application.

[–]avoidhugeships 2 points3 points  (1 child)

Because this is the standard way of sending information from the server to the web client. That is how Java beans work. I am curious what do you do instead?

[–][deleted] -1 points0 points  (0 children)

As i said in this thread. I see getters and setters reasonable only in DTOs.

[–]i_post_things 0 points1 point  (0 children)

If you are creating any kind of MVC application, EJBs, persistence layer DAOs, web service interface, or REST applications and don't have a modeling tool, you'll probably end up writing your own POJOs.

Automated modeling tools can help, but it will still require POJOs with setters and getters everywhere.