RE: [announce] BeanForm 0.6

2006-11-13 Thread Carlos.Fernandez
Daniel,

Why does the POJO used by beanform need to be persisted?

As per component reference:

The Java bean to be displayed by the component; any old POJO. The bean 
specified must be marked persistent in the page specification.

Carlos

-Original Message-
From: DJ Gredler [mailto:[EMAIL PROTECTED] 
Sent: Sunday, November 12, 2006 6:29 PM
To: Tapestry users
Subject: [announce] BeanForm 0.6


Hi all,

The latest release of BeanForm, the single-line POJO editor component, is
now available for download. Below is a list of changes since the last
version. I made a special trip to Spain to get the Spanish translation
strings (my wife thought it was a vacation), so I hope someone finds them
useful ;-) Special thanks to Grzegorz Mrówka and Andreas Andreou for
translations and suggestions!

Happy hacking,

Daniel Gredler



Changes:

 - When moving values from submitted form to properties, only instantiate
null elements of recursive properties when values submitted are not null.
 - Base input field ids on property names.
 - Add pseudo properties as a way of mixing custom fields with bean fields.
 - Make it easier for multi-field binding overrides using OGNL to refer to
the current property.
 - Remove non-threadsafe use of SimpleDateFormat in the Hibernate Validator
integration code.
 - Add support for @Pattern Hibernate Validator annotation.
 - Use PropertySelection component for enum bean properties.
 - Add Polish translation. Thanks to Grzegorz Mrówka.
 - Add Greek translation. Thanks to Andreas Andreou.
 - Add French translation.
 - Add Spanish translation.


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]



Re: [announce] BeanForm 0.6

2006-11-13 Thread DJ Gredler

Hi Carlos,

If the bean is not marked persistent, it will be null on form rewind when
the BeanForm tries to set its property values. Another option may be to
implement PageBeginRenderListener and ensure the bean is initialized inside
the pageBeginRender(PageEvent) method (I've never tried it though). Let me
know if you experiment with alternate solutions.

Take care,

Daniel


On 11/13/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:


Daniel,

Why does the POJO used by beanform need to be persisted?

As per component reference:

The Java bean to be displayed by the component; any old POJO. The bean
specified must be marked persistent in the page specification.

Carlos

-Original Message-
From: DJ Gredler [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 12, 2006 6:29 PM
To: Tapestry users
Subject: [announce] BeanForm 0.6


Hi all,

The latest release of BeanForm, the single-line POJO editor component, is
now available for download. Below is a list of changes since the last
version. I made a special trip to Spain to get the Spanish translation
strings (my wife thought it was a vacation), so I hope someone finds them
useful ;-) Special thanks to Grzegorz Mrówka and Andreas Andreou for
translations and suggestions!

Happy hacking,

Daniel Gredler



Changes:

- When moving values from submitted form to properties, only instantiate
null elements of recursive properties when values submitted are not null.
- Base input field ids on property names.
- Add pseudo properties as a way of mixing custom fields with bean fields.
- Make it easier for multi-field binding overrides using OGNL to refer to
the current property.
- Remove non-threadsafe use of SimpleDateFormat in the Hibernate Validator
integration code.
- Add support for @Pattern Hibernate Validator annotation.
- Use PropertySelection component for enum bean properties.
- Add Polish translation. Thanks to Grzegorz Mrówka.
- Add Greek translation. Thanks to Andreas Andreou.
- Add French translation.
- Add Spanish translation.


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]




[announce] BeanForm 0.6

2006-11-12 Thread DJ Gredler

Hi all,

The latest release of BeanForm, the single-line POJO editor component, is
now available for download. Below is a list of changes since the last
version. I made a special trip to Spain to get the Spanish translation
strings (my wife thought it was a vacation), so I hope someone finds them
useful ;-) Special thanks to Grzegorz Mrówka and Andreas Andreou for
translations and suggestions!

Happy hacking,

Daniel Gredler



Changes:

- When moving values from submitted form to properties, only instantiate
null elements of recursive properties when values submitted are not null.
- Base input field ids on property names.
- Add pseudo properties as a way of mixing custom fields with bean fields.
- Make it easier for multi-field binding overrides using OGNL to refer to
the current property.
- Remove non-threadsafe use of SimpleDateFormat in the Hibernate Validator
integration code.
- Add support for @Pattern Hibernate Validator annotation.
- Use PropertySelection component for enum bean properties.
- Add Polish translation. Thanks to Grzegorz Mrówka.
- Add Greek translation. Thanks to Andreas Andreou.
- Add French translation.
- Add Spanish translation.


Homepage: http://beanform.sourceforge.net/
Component Reference: http://beanform.sourceforge.net/component-reference.html

Change History: http://beanform.sourceforge.net/changes-report.html