{"blog_title":"Fight the Future","author_name":"jyukutyo","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.sakatakoichi.com%2Fentry%2F20080201%2F1201868939\" title=\"Introducing Apache Wicket\u306e\u8d85\u610f\u8a33(6) - Fight the Future\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","title":"Introducing Apache Wicket\u306e\u8d85\u610f\u8a33(6)","image_url":"http://www.theserverside.com/tt/articles/content/IntroducingApacheWicket/images/clip_image007.jpg","author_url":"https://blog.hatena.ne.jp/jyukutyo/","description":"http://www.theserverside.com/tt/articles/article.tss?l=IntroducingApacheWicket Application(\u30a2\u30d7\u30ea\u30b1\u30fc\u30b7\u30e7\u30f3) Unlike most web application frameworks, Wicket doesn't use XML for configuration. Other than minimal configuration in the web.xml deployment descriptor, all application configuration resides in your \u2026","published":"2008-02-02 14:28:59","provider_name":"Hatena Blog","provider_url":"https://hatena.blog","blog_url":"https://www.sakatakoichi.com/","width":"100%","url":"https://www.sakatakoichi.com/entry/20080201/1201868939","categories":["translation"],"height":"190","type":"rich","version":"1.0"}