[jira] Updated: (TAP5-105) Defining a component in the class that does not appear in the template should be an exception (not a logged, and ignored, warning)

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-105:
--------------------------------------

    Summary: Defining a component in the class that does not appear in the template should be an exception (not a logged, and ignored, warning)  (was: No error / warning when using @Component Form instead of BeanEditForm)

I'm very sure that you would see a warning for this in the current code, but (since warnings are always ignored), I'm upgrading it to a thrown exception.

> Defining a component in the class that does not appear in the template should be an exception (not a logged, and ignored, warning)
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-105
>                 URL: https://issues.apache.org/jira/browse/TAP5-105
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.0.15
>            Reporter: Christoph Jäger
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org