So this is the first time I've looked at the wicket booking app. Lots of questions...
It seems every wicket HTML page has a backing class (seems similar to ASP.NET code-behind files). Is this a hard requirement with wicket views? That class must extend org.apache.wicket.markup.html.WebPage and must not be a SFSB. Is this correct?
how to use a dataTable in Wicket? the below html snippet in main.html is very ugly/lengthy in comparison to the JSF/RF equivalent.
The usage of inner classes in classic JSF/RF/Seam/EJB3 development is somewhat foreign and generally unused.
So somebody plz explain how the dataTable population works.
private WebMarkupContainer hotels;
in the Main.java.
<table id="hotels"> <thead> <tr> <th> Name </th> <th> Address </th> <th> City, State </th> <th> Zip </th> <th> Action </th> </tr> </thead> <tbody> <tr wicket:id="hotel"> <td> <span wicket:id="hotelName">[name]</span> </td> <td> <span wicket:id="hotelAddress">[address]</span> </td> <td> <span wicket:id="hotelCityStateCountry">[city, state, country]</span> </td> <td> <span wicket:id="hotelZip">[zip]</span> </td> <td> <a wicket:id="viewHotel">View Hotel</a> </td> </tr> </tbody> </table>
After perusing the entire class, this seems more complicated than JSF/RF but perhaps wicket does not have the life cycle getter/setter multiple-calls problem that JSF has.
Instead of using just one backing bean (e.g. one SFSB) for your view/facelet, now there is an additional class.
What exactly is/are the advantage(s) of using wicket with Seam? How bout the disadvantages?