containing GUI components (like text fields, radio buttons, drawing areas, etc…), in Wicket we have a WebPage instance which represents the physical web page containing HTML components (pictures, buttons, public class WicketApplication extends WebApplication { @Override public ClassWebPage> getHomePage() { return HomePage.class; } @Override public void init() Application's method getHomePage() seen above. In Wicket a web page is a subclass of org.apache.wicket.WebPage. This subclass must have a corresponding HTML file which will be used by the framework as template

containing GUI components (like text fields, radio buttons, drawing areas, etc…), in Wicket we have a WebPage instance which represents the physical web page containing HTML components (pictures, buttons, public class WicketApplication extends WebApplication { @Override public ClassWebPage> getHomePage() { return HomePage.class; } @Override public void init() Application's method getHomePage() seen above. In Wicket a web page is a subclass of org.apache.wicket.WebPage. This subclass must have a corresponding HTML file which will be used by the framework as template

containing GUI components (like text fields, radio buttons, drawing areas, etc…), in Wicket we have a WebPage instance which represents the physical web page containing HTML components (pictures, buttons, public class WicketApplication extends WebApplication { @Override public ClassWebPage> getHomePage() { return HomePage.class; } @Override public void init() Application's method getHomePage() seen above. In Wicket a web page is a subclass of org.apache.wicket.WebPage. This subclass must have a corresponding HTML file which will be used by the framework as template

containing GUI components (like text fields, radio buttons, drawing areas, etc…), in Wicket we have a WebPage instance which represents the physical web page containing HTML components (pictures, buttons, public class WicketApplication extends WebApplication { @Override public ClassWebPage> getHomePage() { return HomePage.class; } @Override public void init() Application's method getHomePage() seen above. In Wicket a web page is a subclass of org.apache.wicket.WebPage. This subclass must have a corresponding HTML file which will be used by the framework as template

containing GUI components (like text felds, radio buttons, drawing areas, etc...), in Wicket we have a WebPage instance which represents the physical web page containing HTML components (pictures, buttons, forms package helloWorld; import org.apache.wicket.markup.html.WebPage; import org.apache.wicket.markup.html.basic.Label; public class HomePage extends WebPage { public HomePage(){ super(); add(new Label("label" link.Link, but it's more like onClick event listener than a link: public class HomePage extends WebPage { public HomePage(){ add(new Link("id"){ @Override public void

Documentation, Release 1.8.4 crawled(request, response, spider) Logs a message when the crawler finds a webpage. dropped(item, exception, response, spider) Logs a message when an item is dropped while it is Developer Tools is the Inspector feature, which allows you to inspect the underlying HTML code of any webpage. To demonstrate the Inspector, let’s look at the quotes.toscrape.com-site. On the site we have a above the span tag highlighted in the screenshot, you’ll see that the corresponding section of the webpage gets highlighted as well. So now we have a section, but we can’t find our quote text anywhere. The

'item': item, } } crawled(request, response, spider) Logs a message when the crawler finds a webpage. download_error(failure, request, spider, errmsg=None) Logs a download error message from a spider Developer Tools is the Inspector feature, which allows you to inspect the under- lying HTML code of any webpage. To demonstrate the Inspector, let’s look at the quotes.toscrape.com-site. On the site we have a above the span tag highlighted in the screenshot, you’ll see that the corre- sponding section of the webpage gets highlighted as well. So now we have a section, but we can’t find our quote text anywhere. The

'item': item, } } crawled(request, response, spider) Logs a message when the crawler finds a webpage. download_error(failure, request, spider, errmsg=None) Logs a download error message from a spider Developer Tools is the Inspector feature, which allows you to inspect the under- lying HTML code of any webpage. To demonstrate the Inspector, let’s look at the quotes.toscrape.com-site. On the site we have a above the span tag highlighted in the screenshot, you’ll see that the corre- sponding section of the webpage gets highlighted as well. So now we have a section, but we can’t find our quote text anywhere. The

'item': item, } } crawled(request, response, spider) Logs a message when the crawler finds a webpage. download_error(failure, request, spider, errmsg=None) Logs a download error message from a spider Developer Tools is the Inspector feature, which allows you to inspect the under- lying HTML code of any webpage. To demonstrate the Inspector, let’s look at the quotes.toscrape.com-site. On the site we have a above the span tag highlighted in the screenshot, you’ll see that the corre- sponding section of the webpage gets highlighted as well. So now we have a section, but we can’t find our quote text anywhere. The

'item': item, } } crawled(request, response, spider) Logs a message when the crawler finds a webpage. download_error(failure, request, spider, errmsg=None) Logs a download error message from a spider Developer Tools is the Inspector feature, which allows you to inspect the under- lying HTML code of any webpage. To demonstrate the Inspector, let’s look at the quotes.toscrape.com-site. On the site we have a above the span tag highlighted in the screenshot, you’ll see that the corre- sponding section of the webpage gets highlighted as well. So now we have a section, but we can’t find our quote text anywhere. The