I tried explicitly dropping the null constraint at the database level - same
issue - for some reason the parameter is being interpreted as not allowed to be
null...while other fields defined exactly the same way are OK...
ALTER TABLE project ALTER COLUMN details DROP NOT NULL;
I have been looking at the bulletin boards, stack overflow and seems like a
known issue...
should I file JIRA?
On Tuesday, June 17, 2014 12:25 AM, Net Dawg <net.d...@yahoo.com.INVALID> wrote:
Getting this parameter not allowed to be null error. Actually there is no
restriction whatsoever on this parameter.
I have a entity class called "Project" with the field "details",
<t:textArea t:id="details" t:validate="maxlength=255" rows="3" cols="90"
value="entity.details" />
@Entity @Indexed
public class Project
{
@Id @GeneratedValue @DocumentId @NonVisual
private Long id;
@Field
private String details="";
Questions: 1. In text area should there be another attribute? I tried
nulls="default"
2. In entity class, Should there be some type other decorator besides @Field
(the @Parameter is not allowed to experiment with acceptNull=true)
