Hi Brown, I think it is unfair say that Wicket present an unexpected
behavior with the markup, because every functionality are well documented. I
saw some situations where some one complain that the id tag attribute
value was changed. But the Component documentation is clear saying that this
Hi!
1. Hierarchy issues - The hierarchy is very strict and not like the Java
hierarchy. If you want to reference a component, it must be added
properly in the markup and in the java code. This can be caught at
compile time, but it is still takes time getting used to.
Note: I am not saying
wicket does not remove class attributes. perhaps you added an
attributemodifier instead of an attributeappender.
-igor
On Tue, Jul 20, 2010 at 10:38 AM, Brown, Berlin [GCG-PFS]
berlin.br...@primerica.com wrote:
There is a css hell, html hell, java web app hell.
Is there a wicket hell or
