Hi,
as you might have already know from previous discussions, this choice
was done to resolve some issues ( WICKET-5724 and WICKET-5730) related
to the new component queuing feature. To be more precise, even before
this change component queuing turned Enclosure components (those
generated wit <wicket:enclosure> tag) into standard components (they
were auto components in Wicket 6.x).
Now that auto components are no more removed, I think that the biggest
impact on page size comes from TransparentWebMarkupContainer components
which are automatically added by Wicket for those HTML tags that have an
attribute with a relative path (for example <link href="">, <script
src="">, <a href="">, etc...).
As you pointed out this has a negative impact on page size, but so far I
haven't noticed any notable difference with my apps. However it would be
nice to investigate this aspect a little bit more with complex pages and
make some comparison of the page size with 6.x and 7.
Andrea.
Hi,
AFAICS, due to the recents changes committed in 7, auto components are
serialized. I saw a few discussions about this change and I wanted to
point out a consequence of this change.
This causes a slight increase in the serialized page size (see this
commit for instance:
https://github.com/wicketstuff/core/commit/2c09e335d114ab6b988878b0880e0a73caf36c7e
).
I just wanted to point out that it might have a real negative
performance impact on the serialization process of complex pages
heavily based on auto components.
If there are real benefits for this, it might be worth it but I think
it's something to considerate carefully.
