I've been thinking of adding an annotation, perhaps BeanPropertyType that would be used to override the default mechanism for determinng the property type. The property type is used to locate a block to display a property (in BeanDisplay and Grid components) and edit a property (in BeanEditor component, included inside BeanEditForm).
By allowing a specific override, we could then define property types of "longtext" (that would use a TextArea) or even "richtext" that would use some kind of rich text editor on the client side. It would also help with a number of other edge cases, such as is java.sql.Date a date or a date and a time? On Nov 23, 2007 3:33 PM, Eko S.W. <[EMAIL PROTECTED]> wrote: > Hi All, > > I've another (I hope last) > That is, Can we use Text Area for String field in BeanEditor? > > do we have to interfere the TML file? > Thanks in advance for the answer! > -- > Best wishes, > Eko SW > My Heart : http://swdev.blogs.friendster.com/my_blog/ > My Job : http://swdevsoftwareconsulting.blogspot.com > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
