there is @InjectComponent annotations for using Form in java code and leaving BeanEditForm in template...
On Tue, Mar 4, 2008 at 9:37 PM, Christoph Jäger (JIRA) <[email protected]> wrote: > No error / warning when using @Component Form instead of BeanEditForm > --------------------------------------------------------------------- > > Key: TAPESTRY-2233 > URL: https://issues.apache.org/jira/browse/TAPESTRY-2233 > Project: Tapestry > Issue Type: Improvement > Components: tapestry-core > Reporter: Christoph Jäger > Priority: Minor > Fix For: 5.0.10 > > > I just spent quite some time to find a bug in my code. > > In my .tml I use a <t:BeanEditForm>. As soon as I added > @Component > private Form form; > to the corresponding .java file (need to do some validation), the form was > no longer rendered (the rest of the page was there, only the form was > missing). Of course, using > @Component > private BeanEditForm form; > instead fixes the problem. > > It took me long to find the problem, because there was no hint of what I was > doing wrong. Maybe Tapestry could be enhanced to generate some kind of error > message or warning in case of such misaligned component classes, instead of > quietly dropping the form. > > Of course, enhancing the system to be able to use Form instead of > BeanEditForm if you need just the basic features of Form, and not > BeanEditForm in your java code, would be even better, but this seems > difficult, as Form is not a super-class of BeanEditForm. > > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > > --------------------------------------------------------------------- > 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]
