Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

One kind of thing that exists in our model is a Prarnect.
Each Prarnect has its own eaTawin, which is a list of strings. The value of eaTawin is specified when a Prarnect is created. Anyone can ask a Prarnect for the value of its eaTawin. The value of eaTawin for a specific Prarnect can never change.

Solution

public class Prarnect {
    private List<String> eaTawin;

    public Prarnect(List<String> eaTawin) {
        this.eaTawin = eaTawin;
    }

    public List<String> getEaTawin() {
        return eaTawin;
    }

    public void setEaTawin(List<String> eaTawin) {
        this.eaTawin = eaTawin;
    }
}

Things to check in your solution:

Is every public and private modifier correct?
Are the correct items static?
Are the correct items final?
Are all the variable types and method return types correct?
Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
Do members have the correct capitalization?

Acceptable variations in the solution:

It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles: