NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
The Wicket team is proud to announce the availability of
Wicket 1.1
for download! Wicket is a Java, component oriented web application framework that takes simplicity, separation of concerns and ease of use to a whole new level. Wicket web applications consist of HTML markup and Java classes. No strange languages, no strange markup, no configuration files, no specialized, expensive tools: just Java, HTML and you.
This Wicket version contains a lot of improvements from the 1.0 version. New features include:
Simplified feedback and validation - enables custom feedback strategies
Live Component Reference - the examples project contains a component reference showing how to use the components.
JavaScript and CSS support for components - contribute JavaScript and CSS from your component to the using page
Markup Inheritance - enables template pages and components
Inclusion of external markup
Simplified Choice component
Advanced Table components - easily generate pageable/sortable tables backed by database or any other datasource in wicket-extensions (graduated components from wicket-contrib-dataview)
Less dependencies - we removed several library dependencies
Customizable Form handling - easy for quick forms, easily enables full custom form processing
Improved resource handling
Date picker component - will not get you dates, but a JavaScript and text field enabled localized calendar component.
Improved URL handling
AJAX request handling support - support for two leading AJAX JavaScript libraries is available as separate downloads from our Wicket Stuff project: scriptaculous and DOJO toolkit
The Wicket team wishes to extend their gratitude to the user and developer community for their testing efforts and help, making this release a reality!
The Wicket 1.1 distribution can be downloaded from the SourceForge servers by following
this link
.
This might seem like a silly question, but is it possible to successfully leverage Wicket by not making use of it's tag libraries? We are currently working on a project that we are trying hard to keep pure XHTML/CSS on the front end, and have liked what we've seen from Wicket, but I know that wicket is a component-based framework and didn't know how critical it was we use the taglibs in order to keep the view/model connection.
I'd also love to hear feedback from anyone that is currently leveraging wicket in a situation like ours and how they are working around that issue, maybe it's not even a problem?
Your question regards the
wicket:id
and
wicket:xxx
tags: they are
not
taglibs, but they are namespaced tags for identifying wicket components. It is possible to introduce the wicket 1.0 to your [x](ht)?ml using a DTD declaration (we have one on the website). We currently do not have a XML schema of the Wicket tags. We would like an XML expert to look into that someday.
The wicket:xxx tags can be stripped when rendering your webpages, so they don't show up in the final page.
The tags/attributes are there in order to allow your designer to use the html/xml 'ID' attribute without problem, so unlike some other frameworks we don't use any of the CSS selectable xml/html/xhtml tags for our own pleasure, and give the designer full control on using the CSS selectors.
So, since I was not able to find a real documentation beside some release notes, where is one? (I read some good stuff in a blog some time ago, iirc, must be integrated in a wiki now?)
Thanks for taking the effort and look at the website. It is flawed and I sincerely apoligize for having those dead links there. It is something that is gnawing at me for some time, but I haven't gotten around to fixing the actual problem yet. I've collected some additional links for you to peruse below.
I sincerely hope you haven't lost interest because of these links.
> So, since I was not able to find a real documentation
> beside some release notes, where is one? (I read some
> good stuff in a blog some time ago, iirc, must be
> integrated in a wiki now?)
I admit that the wicket-1.0 and wicket-1.1 stable sites are not completely working crosslink-wise. It is not the way I would like it to be. However inside the sites things
do
work out. The website is generated using maven and I still have to flesh out some quirks regarding these links that are external to the actual deployment site (i.e. the wicket-releasenumber folder), but not to the http://wicket.sourceforge.net site.
I just fixed all links in the navigation menu for the
Wicket 1.1
website. I didn't have time to go through all documents and find all links referencing dead links.
In addition to what Martijn just said, I simply downloaded Wicket-examples 1.1, took the war and dropped it into Tomcat and then slowly clicked through it, one at a time, link by link... I think I just learned more about wicket in the last 20mins than I have in the last month... very easy to follow and really exciting to be honest, this looks like just the type of approach I was looking for.
http://www.wicket-library.com/examples/ HTTP Status 404 - /examples/
type Status report
message /examples/
description The requested resource (/examples/) is not available.
Anyway, thanks for fixing the links, the wiki provides what I was looking for
I have been using Wicket for the last couple of months. I upgraded to 1.1 this month and have been using some of the AJAX functionality using Scriptaculous, specifically the auto complete text field.
My background has been in developing J2EE applications with Swing clients. This is why Wicket was a natural selection for me when I researched the available web frameworks. It is component based and just made total sense to me.
My development environment is Wicket 1.1, Spring 1.2, Hibernate 3.0, MySQL 4.1, Tomcat 5.5, Scriptaculous 1.5, and Eclipse 3.1.
In a little over 160 hours I have developed a fairly robust web application using this environment. This is a data-driven business application and not a traditional website. I am happy with the user interface which is approaching desktop usability with the AJAX features.
I have many things to learn, especially concerning session serialization and load testing.
Thanks to the Wicket team for developing a great framework.
I'd like to add to this, I finally bit the bullet and put together a silly registration system that used Wicket/Hibernate and I must say, the fact that my pages were straight HTML, no tags anywhere and all I had were wicket:id's scattered in a few places and had a fully functional system was just a dream. Wicket was so simply to pickup, when you follow the tutorial, everything works as you would imagine it to work, no monkey business. I'd also like to say that detailed error/exception screen that wicket provides is so slick, it narrows down exactly in my code where I have problems. Occasionally there are vague errors, but that's due to vague problems, no fault of Wicket.
Wicket 1.1 final available
URL: Wicket Web framework
At 5:31 PM on Oct 31, 2005, Martijn Dashorst
wrote:
Fresh Jobs for Developers Post a job opportunity
The Wicket team is proud to announce the availability of Wicket 1.1 for download! Wicket is a Java, component oriented web application framework that takes simplicity, separation of concerns and ease of use to a whole new level. Wicket web applications consist of HTML markup and Java classes. No strange languages, no strange markup, no configuration files, no specialized, expensive tools: just Java, HTML and you.
This Wicket version contains a lot of improvements from the 1.0 version. New features include:
The Wicket team wishes to extend their gratitude to the user and developer community for their testing efforts and help, making this release a reality!
The Wicket 1.1 distribution can be downloaded from the SourceForge servers by following this link .
The Wicket 1.1 release documentation can be found at: http://wicket.sourceforge.net/wicket-1.1
13 replies so far (
Post your own)
Re: Wicket 1.1 final available
This might seem like a silly question, but is it possible to successfully leverage Wicket by not making use of it's tag libraries? We are currently working on a project that we are trying hard to keep pure XHTML/CSS on the front end, and have liked what we've seen from Wicket, but I know that wicket is a component-based framework and didn't know how critical it was we use the taglibs in order to keep the view/model connection.I'd also love to hear feedback from anyone that is currently leveraging wicket in a situation like ours and how they are working around that issue, maybe it's not even a problem?
Re: Wicket 1.1 final available
Your question regards the wicket:id and wicket:xxx tags: they are not taglibs, but they are namespaced tags for identifying wicket components. It is possible to introduce the wicket 1.0 to your [x](ht)?ml using a DTD declaration (we have one on the website). We currently do not have a XML schema of the Wicket tags. We would like an XML expert to look into that someday.The wicket:xxx tags can be stripped when rendering your webpages, so they don't show up in the final page.
The tags/attributes are there in order to allow your designer to use the html/xml 'ID' attribute without problem, so unlike some other frameworks we don't use any of the CSS selectable xml/html/xhtml tags for our own pleasure, and give the designer full control on using the CSS selectors.
I hope this takes away some of your concerns?
Re: Wicket 1.1 final available
Martijn,Thank you very much this does answer all my questions as well as correct some misunderstandings I had.
Re: Wicket 1.1 final available
I hope to see you on the mailinglist thenRe: Wicket 1.1 final available
Hm, let's take a look at the navigation:http://wicket.sourceforge.net/wicket-1.1/wiki
not working
http://wicket.sourceforge.net/wicket-1.1/wicket-1.1/index.html
not working
http://wicket.sourceforge.net/wicket-1.1/wicket-1.0/index.html
not working
http://wicket.sourceforge.net/wicket-1.1/wicket-extensions/index.html
not working
http://wicket.sourceforge.net/wicket-1.1/wicket-quickstart/index.html
not working
So, since I was not able to find a real documentation beside some release notes, where is one? (I read some good stuff in a blog some time ago, iirc, must be integrated in a wiki now?)
Re: Wicket 1.1 final available
Heribert,Thanks for taking the effort and look at the website. It is flawed and I sincerely apoligize for having those dead links there. It is something that is gnawing at me for some time, but I haven't gotten around to fixing the actual problem yet. I've collected some additional links for you to peruse below.
I sincerely hope you haven't lost interest because of these links.
> So, since I was not able to find a real documentation
> beside some release notes, where is one? (I read some
> good stuff in a blog some time ago, iirc, must be
> integrated in a wiki now?)
Have you tried:
http://wicket.sourceforge.net/wicket-1.1/Examples.html
Giving a nice overview of the way Wicket applications are in code.
http://wicket.sourceforge.net/wicket-1.1/Introduction.html
Giving the ideas on why Wicket was created.
http://wicket.sourceforge.net/wicket-1.1/apidocs
Showing the api documentation for Wicket
http://www.wicket-library.com/examples/
For live examples on display and
http://www.wicket-library.com/wicket-examples/compref
For a live reference guide of most standard Wicket components
http://wicket.sf.net
Being the main wicket site, on which for instance the link to the wiki:
http://wicket.sf.net/wiki
does work.
As does the link to the Wicket Quickstart project:
http://wicket.sf.net/wicket-quickstart
and the Wicket Extensions project:
http://wicket.sf.net/wicket-extensions
I admit that the wicket-1.0 and wicket-1.1 stable sites are not completely working crosslink-wise. It is not the way I would like it to be. However inside the sites things do work out. The website is generated using maven and I still have to flesh out some quirks regarding these links that are external to the actual deployment site (i.e. the wicket-releasenumber folder), but not to the http://wicket.sourceforge.net site.
With regards,
Martijn
Re: Wicket 1.1 final available
I just fixed all links in the navigation menu for the Wicket 1.1 website. I didn't have time to go through all documents and find all links referencing dead links.Re: Wicket 1.1 final available
In addition to what Martijn just said, I simply downloaded Wicket-examples 1.1, took the war and dropped it into Tomcat and then slowly clicked through it, one at a time, link by link... I think I just learned more about wicket in the last 20mins than I have in the last month... very easy to follow and really exciting to be honest, this looks like just the type of approach I was looking for.Re: Wicket 1.1 final available
http://www.wicket-library.com/examples/HTTP Status 404 - /examples/
type Status report
message /examples/
description The requested resource (/examples/) is not available.
Anyway, thanks for fixing the links, the wiki provides what I was looking for
Re: Wicket 1.1 final available
Ah yes... I always type that one in wrong: it should have read http://www.wicket-library.com/wicket-examplesRe: Wicket 1.1 final available
I have been using Wicket for the last couple of months. I upgraded to 1.1 this month and have been using some of the AJAX functionality using Scriptaculous, specifically the auto complete text field.My background has been in developing J2EE applications with Swing clients. This is why Wicket was a natural selection for me when I researched the available web frameworks. It is component based and just made total sense to me.
My development environment is Wicket 1.1, Spring 1.2, Hibernate 3.0, MySQL 4.1, Tomcat 5.5, Scriptaculous 1.5, and Eclipse 3.1.
In a little over 160 hours I have developed a fairly robust web application using this environment. This is a data-driven business application and not a traditional website. I am happy with the user interface which is approaching desktop usability with the AJAX features.
I have many things to learn, especially concerning session serialization and load testing.
Thanks to the Wicket team for developing a great framework.
Re: Wicket 1.1 final available
Hi Brent,Thanks for sharing your experience. I'm always glad to hear when people use our framework and are enjoying it!
Re: Wicket 1.1 final available
I'd like to add to this, I finally bit the bullet and put together a silly registration system that used Wicket/Hibernate and I must say, the fact that my pages were straight HTML, no tags anywhere and all I had were wicket:id's scattered in a few places and had a fully functional system was just a dream. Wicket was so simply to pickup, when you follow the tutorial, everything works as you would imagine it to work, no monkey business. I'd also like to say that detailed error/exception screen that wicket provides is so slick, it narrows down exactly in my code where I have problems. Occasionally there are vague errors, but that's due to vague problems, no fault of Wicket.