[
https://issues.apache.org/jira/browse/WICKET-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677985#comment-15677985
]
Martin Grigorov commented on WICKET-4978:
-----------------------------------------
[~tobiashaupt] Now I've checked your attached classes and I think there is no
need to create a new ticket.
Your requirement could be easily achieved by overriding #onComponentTag():
{code}
@Override protected void onComponentTag(ComponentTag tag)
{
tag.setName("table");
tag.append("class", "MyCSSClass", " ");
}
{code}
No need of all the rewriting of the markup.
Please use the mailing lists if you want to discuss more your idea. There are
more people subscribed there so we could get more feedback how to make Wicket
better!
Thank you!
> Add possibility to force usage of (renderable) tag for own Components
> ---------------------------------------------------------------------
>
> Key: WICKET-4978
> URL: https://issues.apache.org/jira/browse/WICKET-4978
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Reporter: Peter Parson
> Attachments: wicketPanel_Tag_Rewriting.zip
>
>
> Sometimes, Components don't work as expected when not used with a DOM element.
> This generates bugs, which are often and especially only visible on ajax
> interaction.
> Common scenario: updating a component via Ajax which is used with
> wicket:container or setRenderBodyOnly(true). Or updating those (non-existent)
> DOM element with HTML attributes.
> To allow for fail-fast behavior, I suggest to add an overridable getter to
> indicate that the component must be rendered as DOM element, e.g.
> isDomElementMandatory().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
