we now use our own namespace for border/body tags like <wicket:border> and <wicket:body/>, which are perfectly legal tags in XHTML (provided that we come up with the right schema, which i think is still an open item for 1.0 final).
however, if you prefer not to serve up XHTML, you can strip out all wicket-related tags from your output using ApplicationSettings.setStripWicketTags(). also, if you just use ApplicationSettings.configure("development") you will see wicket tags in your output (which are helpful in debugging). if you switch to "deployment" configuration wicket tags will be stripped. the code for this in ApplicationSettings looks like this:
/**
* Configures application settings for a given configuration type.
*
* @param configurationType
* The configuration type. Must currently be either "development"
* or "deployment".
*/
public final void configure(final String configurationType)
{
configure(configurationType, "src/java");
}
/**
* Configures application settings for a given configuration type.
*
* @param configurationType
* The configuration type. Must currently be either "development"
* or "deployment".
* @param sourceFolder
* If configurationType is "development", then this folder will
* be polled for resource changes
*/
public final void configure(final String configurationType, final String sourceFolder)
{
if ("development".equalsIgnoreCase(configurationType))
{
if (sourceFolder != null)
{
setSourcePath(new Path(new Folder(sourceFolder)));
setResourcePollFrequency(Duration.ONE_SECOND);
}
setComponentUseCheck(true);
setStripWicketTags(false);
}
else if ("deployment".equalsIgnoreCase(configurationType))
{
setComponentUseCheck(false);
setStripWicketTags(true);
}
else
{
throw new IllegalArgumentException(
"Invalid configuration type. Must be \"development\" or \"deployment\".");
}
}
Kamil Rembalski wrote:
Hi,
I remember that there was a discussion about web sites where only a small part of the view changes across the pages, and most of it (menus, headers, etc. stays the same). The default solution was to use a border, but I remember that it required a tag that would violate html spec (border tag, containing the whole index page). Here's a simple workaround:
1) crete a index page and markup for it.One of the components will be the content - changing part of the page. In index page constructor, specify all components, but not this one. Trying to create this page will cause an error, but it will be never created.
2) Implement the pages you need by extending index page and specifying the content component / components.
plain, object-oriented and easy.
regards, Kamil
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
