How to use jTable in java?

Its OK to use public field in Java in this case. Agree?

• I am defining a "wire format" of a business object. This wire format is going to be serialized to JSON, and sent across the wire to a RESTful API consumers (e.g. JavaScript in HTML page). I experimented with the JAX-RS processing. The following two patterns yield the exact same JSON output: [Pattern A] public class Student {   public String firstName; } [Pattern B] public class Student {   private String firstNameXYZ; // made internal name a bit weired to emphasize information hiding.   public String getFirstName {     return this.firstNameXYZ;   }   public void setFirstName(String firstName) {     this.firsNameXYZ = firstName;   } } I want to use [Pattern A] because of the following reasons: Unlike regular Java-binding, the client binds to this data via JSON. So the binding is not as strong as Java-to-Java binding, so exposing public fields is not as bad as Java-to-Java binding scenario (where encapsulating with getter/setter is very useful for achieving loose-coupling) This is for wire format. Basically a "struct" with almost no behavior (there could be some translation between Enum and String etc, but no "behavior" in the sense that it causes state change be receiving messages etc.) Because this is for defining data to be consumed via REST, we plan to support "legacy" version as we continue to develop the API. That is: we plan *not* to remove any field. We continue to add new fields and recommend client developers to not to use "obsolete/outdated" fields, but nonetheless we won't remove it. Any input appreciated!

• Answer:

  What you describe here has nothing to do with the fact you're planing a REST WS , or use JSON , really. But,.. it has to do with the fact you're using an OBJECT ORIENTED language. And one of OO core concept , called "encapsulation" , guides you to use pattern b. Good luck.