Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If a tag's written like this,

Code Block

<span wicket:id="name"/>

the tag's not rendered, whereas if it's written like this

Code Block

<span wicket:id="name">name</span>

it is.
The rationale is that we do not automatically convert

Code Block

<span/>

into

Code Block

<span></span>

because that's too much "behind-the-scenes" magic for user to be happy with. As a result, as a

Code Block

<span/>

has no body, onComponentBody() isn't called and nothing is rendered!

...

Yes, it is. However, we must rely on the Maven project to update their repository with the latest releases, resulting in some lag. If you need them hot and fresh, you can use the wicket Maven 2 repository by adding the the following to your project's pom.xml:

Code Block
xml
xml
  <repositories>
    <repository>
      <id>wicket</id>
      <name>Wicket repository</name>
      <url>http://wicket.sourceforge.net/maven2</url>
    </repository>
  </repositories>

...

Code Block
xml
xml
<init-param>
            <param-name>configuration</param-name>
            <param-value>DEPLOYMENT</param-value>           
</init-param>

How do I know in what mode (DEVELOPMENT/DEPLOYMENT) my application runs?

...

Also, if the configuration parameter in the web.xml is set to DEPLOYMENT, these checks are disabled.

Answer provided courtesy Igor Vaynberg

Which browsers have been tested with Wicket AJAX?

...

  • a normal request, where the page map name parameter is provided as a part of the bookmarkable page request parameter:
    Code Block
    
    myapp?wicket:bookmarkablePage=myPageMap:somepackage.MyPage
    
  • a request to a mounted URL, where the page map parameter is provided as a path encoded parameter:
    Code Block
    
    /myapp/mountedpage/param1/value1/wicket:pageMapName/myPageMap
    

What is the future of onAttach and onDetach methods?

...

Write clean HTML with CSS targeted toward the various mobile clients that you wish to support. More info can be found on the Mobile Devices page.

What about performance and scalability?

Wicket performance is actually quite good under stress. Remember though that in many real-world application your bottleneck will be in business or database layer.

Wicket benchmark can be found here: wicket-1.x-benchmark.

You should also search wicket-user mailing list for performance and scalability or simply use performance-scalability-tipsas your starting point.