[WICKET-6229] Introduce a new setting in ExceptionSettings to control whether to throw exception or log a WARN when requesting for markup id on non-renderable component

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 7.4.0
• Fix Version/s: 8.0.0-M2, 7.5.0
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Tzvetanov Grigorov
• Created: 19/Aug/16 08:51
• Updated: 18/Nov/16 22:32
• Resolved: 23/Aug/16 19:42

Description

From dev@ (http://markmail.org/message/shqbyreferrpxv3q):

What do you think on adding a new setting to ExceptionSettings that says whether to log a WARN (default, as it does now) or to throw exception when setOutputMarkupId/setOutputMarkupPlaceholderTag() are used on component with #setRenderBodyOnly(true) or attached to <wicket:container> ?

I've had few occasions in the past few months where colleagues of mine use <wicket:container> and later try to update it with Ajax. The WARN log is buried amongst other logs (and developers usually simply ignore WARNs) and I see it is hard for them to find out the reason.

If the setting proves to be useful then we can throw an exception in DEV mode and log a WARN in PROD mode.

https://github.com/apache/wicket/blob/bec52515f1bb2570f09140ba6f457c369f3a56b1/wicket-core/src/main/java/org/apache/wicket/Component.java#L4019-L4035

Issue Links

• supercedes: WICKET-4978 Add possibility to force usage of (renderable) tag for own Components