Thanks but we try to avoid overriding Tapestry classes whenever possible.. in this case we wouldn't really be changing anything except what "mode" defaults to so I would consider it an override rather than a custom component. Overrides make upgrading tricky and introduce subtle bugs that take forever to track down.
I believe Insert used to behave in 4.0 the same way it behaves in 4.1 with mode="ognl:@[EMAIL PROTECTED]". It would be nice to have an application-wide setting for this, if nothing else, for backwards compatibility sake. -----Original Message----- From: Norbert Sándor [mailto:[EMAIL PROTECTED] Sent: Monday, February 12, 2007 3:40 PM To: Tapestry users Subject: Re: @Insert default mode Maybe override the Insert component in the .application file with your custom one. N. Ben Dotte írta: > Does anyone know if there is a way to specify a default mode for the > Insert component? When we upgraded to Tapestry 4.1 we ended up having to > specify InsertMode.BREAK every place we use it but that ends up looking > pretty ugly in the many places we use Insert > (mode="ognl:@[EMAIL PROTECTED]"). > > > > It would be nice if there was some way to configure a default value for > this if there isn't already. > > > > Thanks, > > Ben > > > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.441 / Virus Database: 268.17.37/682 - Release Date: 2007.02.12. > 13:23 > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
