Sorry, no. It was semi-interesting trying to achieve compatibility with both 4.0 and 4.1... Maintaining compatibility with all 3 versions would probably be nigh impossible.
Of course, nothing stops you from forking a Tap3 version :-) On 9/14/06, Mark Stang <[EMAIL PROTECTED]> wrote:
I don't suppose there is a version for 3.x? Mark J. Stang Senior Engineer/Architect office: +1 303.468.2900 mobile: +1 303.507.2833 Ping Identity -----Original Message----- From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] Sent: Wed 9/13/2006 8:10 PM To: Tapestry users Subject: Re: [announce] BeanForm 0.4 Oops...I've fixed that now. BeanForm should show up linked in directly from the main site whenever the apache servers sync up. On 9/13/06, Martin Strand <[EMAIL PROTECTED]> wrote: > > Nice work! :) > I was actually just working on my own beanform when I came across yours > about two weeks ago. Now I use yours instead, I just subclassed it to add > a few app specific features. > Do you have a public svn repo somewhere? > > Martin > > On Wed, 13 Sep 2006 23:15:12 +0200, D&J Gredler <[EMAIL PROTECTED]> > wrote: > > > Hi all, > > > > I have just released the latest version of BeanForm, a single-line POJO > > editor component: > > > > span jwcid="@bf:BeanForm" bean="ognl:pojo" save="listener:save" > > delete="listener:delete" > > > > The above line of code gets you a form that: > > > > * calls your page's save() method when submitted for save > > * calls your page's delete() method when submitted for delete > > * gives you a TextField for each of the bean's string and numerical > > properties > > * gives you a Checkbox for each of the bean's boolean properties > > * gives you a DatePicker for each of the bean's date properties > > * automatically disables fields for read-only properties > > > > If you are using Java Persistence API (EJB3) annotations and/or > Hibernate > > Validator annotations, the BeanForm component also: > > > > * infers validation strings for annotated properties > > * uses TextAreas instead of TextFields for annotated string > > properties > > whose maximum length is over 255 characters > > > > Some other important features: > > > > * EJB3 and Hibernate Validator support is optional and enabled > > automatically at runtime only when appropriate > > * you can use a BeanForm inside a Form component, in which case the > > BeanForm will not emit a second form tag > > * you can explicitly specify which properties to display, as well as > > their validation strings > > * when specifying properties explicitly, they may be recursive (" > > person.address.city.name", for example) > > * you can override the input components used to edit properties > > * support for canceling and refreshing forms > > * support for localization > > > > Starting with version 0.4, BeanForm should work with both Tapestry 4.0 > > and > > Tapestry 4.1. > > I should also note that starting with version 0.4, BeanForm requires the > > tapestry-prop library, available at > > > http://howardlewisship.com/repository/com/javaforge/tapestry/tapestry-prop/0.1.1/ > > . > > > > Give it a whirl and let me know if you have any problems, comments or > > suggestions. > > > > Take care, > > > > Daniel Gredler > > > > ---------------------------- > > Homepage: http://beanform.sourceforge.net/ > > Component Reference: > > http://beanform.sourceforge.net/component-reference.html > > Change History: http://beanform.sourceforge.net/changes-report.html > > ---------------------------- > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
