private field access instead of property

[laliluna.usenet.laliluna.de]

Hello,
with Hibernate it is a best practise to use private setter for the id, as this should only be set by Hibernate (in case of generated ids).

Is there any way to convince
the javax.el to use private field access as well?

Best Regards

Sebastian

@Id
@GeneratedValue
private Long id;

public Long getId(){
return this.id;
}
private void setId(Long id);

Error message in case you try to use a model with private setter in an edit form.

javax.el.PropertyNotFoundException: Property 'id' not writable on type java.lang.Long
     at javax.el.BeanELResolver$BeanProperty.write(BeanELResolver.java:247)
     at javax.el.BeanELResolver$BeanProperty.access$100(BeanELResolver.java:209)
     at javax.el.BeanELResolver.setValue(BeanELResolver.java:106)
     at javax.el.CompositeELResolver.setValue(CompositeELResolver.java:68)
     at com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:93)
     at org.apache.el.parser.AstValue.setValue(AstValue.java:114)
     at org.apache.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:249)
     at com.sun.faces.application.ValueBindingValueExpressionAdapter.setValue(ValueBindingValueExpressionAdapter.java:141)
     at org.jboss.seam.core.Expressions$1.setValue(Expressions.java:93)

[pmuir]

Don't bind the property to an input control?

[stephen]

with Hibernate it is a best practise ...

Says who? If you annotate the field you do not need any setter at all.

To answer your question: I don't think this is possible at all (without deeply fiddling with the EL implementation).
EL relies on JavaBean-style accessors.