Re: CLOB property, editing the value thru wicket viewer text field instead of download/upload file

For long text fields I use this pattern: private String myLongTextField; @javax.jdo.annotations.Column(allowsNull="true", jdbcType="CLOB", sqlType="LONGVARCHAR") public String getMyLongTextField() { return myLongTextField; } public void setMyLongTextField(final String myLongTextField) {

Re: CLOB property, editing the value thru wicket viewer text field instead of download/upload file

Hi Jeroen, I've used that already, but I have failed thru 2000 chars restriction. Regs,Vladimir 2015-10-07 9:46 GMT+02:00 Jeroen van der Wal : > For long text fields I use this pattern: > > private String myLongTextField; > > @javax.jdo.annotations.Column(allowsNull="true",

Re: CLOB property, editing the value thru wicket viewer text field instead of download/upload file

Hi Jeroen, sorry, I was to fast with my comment, your proposal works also! Many thanks! Regs,Vladimir 2015-10-07 12:52 GMT+02:00 Vladimir Nišević : > Hi Jeroen, I've used that already, but I have failed thru 2000 chars > restriction. > > Regs,Vladimir > > > 2015-10-07 9:46

Re: CLOB property, editing the value thru wicket viewer text field instead of download/upload file

Hmm, sounds like a new requirement. The idea of CLOB really is to represent documents, not for direct editing. As a workaround, could you define a derived non-persisted property and have it update the clob, eg: @PropertyLayout(multiLine=20) @javax.jdo.annotations.NotPersistent public String

Re: CLOB property, editing the value thru wicket viewer text field instead of download/upload file

Hi Dan, that is also absolutely fine for me! Many thanks! Vladimir > Am 06.10.2015 um 16:39 schrieb Dan Haywood : > > Hmm, sounds like a new requirement. The idea of CLOB really is to > represent documents, not for direct editing. > > As a workaround, could you