Catching all feedback messages that aren’t rendered by other feedback panels
There are many times in writing our Wicket applications that we want to render feedback messages close to the component that registered the message - especially in forms. But, we also typically want to display all the other messages in one “catch-all” feedback panel near the top of the page. Sometimes this can be difficult to do, especially if your form component feedback panels are added by borders, etc. Here is one implementation that will allow you to have a single “catch-all” feedback panel on any page.
Read the rest of this entry »
More great reasons to go to ApacheCon US 2009
ApacheCon US 2009 is fast approaching. And for all you Wicket lovers out there, or anybody interested in getting started with Wicket, you know that I will be presenting a one day training as well as an Introduction to Wicket session. So if you haven’t done so already, go sign up!
More info on the Wicket training: www.jeremythomerson.com/blog/2009/07/wicket-training-at-apachecon-us-2009/
CLICK HERE TO REGISTER
But what about more great reasons to register? I’ve put together a list of the sessions that you might want to attend if you are interested in Wicket. Of course, there are many great sessions, and you may (like me) have a hard time choosing. You may be interested in the entire track on Lucene / Hadoop and the family. Or in the business track. But here are some that you may particularly like: Read the rest of this entry »
Wicket Training at ApacheCon US 2009
I am very happy to announce that there will be a one day training course at the 2009 ApacheCon conference in Oakland, CA (USA). Before I tell you more about it, consider the following “top ten” list:
Top Ten Reasons You Should Attend ApacheCon US 2009:
10: Hacking is encouraged at the Apache Hackathon two day event.
9: Free beer! wiki.apache.org/apachecon/ApacheConUs2009Program
8: Meet members of your favorite projects (i.e. me last year getting Martijn to sign my copy of Wicket in Action: see Martijn signing my book)
7: Free two day BarCamp
6: Free meetups three nights of the week
5: It’s always a good time to visit California: oaklandcvb.com/
4: Support the tenth anniversary of the Apache Software Foundation and the many other great projects that will be there.
3: Did I mention FREE BEER?
2: Two attendees in the class will receive FREE copies of Wicket in Action
1: WICKET TRAINING! (more info)
More details will be coming soon, but if you are looking to get your feet wet with Wicket, you should certainly start making plans now to attend the 2009 US ApacheCon, and the Wicket training class that will be held. Those who register early get discounts, too!
The class will consist of fast-moving explanations of core design principles, Wicket components, and “The Wicket Way”, and each section will be followed by a coding practice where you can put into use what you just learned. We will focus on laying a foundation - how to use Wicket, create pages, organize your application, and create a Wicket application.
We will cover the following:
- The fundamentals of Wicket
- Handling data / working with objects and models
- Standard components provided by framework
- Containers / Application / Session / Page
- Effective code reuse strategies
ApacheCon site: www.us.apachecon.com
November 2-6, 2009 in Oakland, CA. Classes will be held on Monday and Tuesday. Wednesday through Friday will be for the conference sessions. The Wicket class will be held on Tuesday.
Follow ApacheCon on Twitter: twitter.com/apachecon
I’m now a Wicket core developer
My intention is not to blow my own horn, but I was so excited to have been asked to join the Wicket development team (link) that I knew it was time to dust off the old blog and start trying to write some articles again. And no more than an hour after it was announced, I was asked about when 1.5 would be released! (a well-meaning joke). I have a lot of respect for all of the Wicket developers who have brought the great framework this far, and I hope that I will do well in assisting to carry the torch further.
Thank you to everyone who has contributed countless hours to making Wicket a great product! Now it’s time to roll up my sleeves and get to work!
Wicket Stuff Reorganization
So last week and this weekend I was swamped spending pretty much every night trying to get the Wicket Stuff project organized. When I started, the trunk of Wicket Stuff had over 85 folders (subprojects) in it. It was a mess. Tons of these have been abandoned over time, with no work done since the 1.3 release of Wicket was cut and trunk changed to 1.4 development. The biggest problem I wanted to address (and the community overwhelmingly agreed) was that there was no standard release pattern for nearly any WicketStuff project.
What we decided
It was decided to create a “core” project for WicketStuff where other projects would reside under it (using Maven modules). We would get this core building and releasing snapshots in the wicketstuff.org maven repo so that if you were developing against Wicket 1.4-SNAPSHOT, you could also do the same for the WicketStuff projects. Then, whenever a numbered release of Wicket came out (i.e. 1.4-rc2 soon), we would cut a release with the same number for WicketStuff. This should make it much easier to use the WicketStuff projects, many of which have never had any numbered releases (you always had to compile your own to use).
What was accomplished
Here’s a quick summary of what was accomplished:
- 21 projects were moved into the core (including “examples” projects) (UPDATE: more are being migrated - this number has grown)
- 32 folders were removed from trunk into the attic
- All that in over 73 commits!
- This left us with around 30-something folders left in trunk - and hopefully most of those will move into the core project.
Here’s a status page that I’ll be updating as more progress is made:
wicketstuff.org/confluence/display/STUFFWIKI/WicketStuff+Reorg+-+Status+and+List+of+Changes
Wicket in Action Book Signing
- Martijn signs my book!
Yes, it’s dumb, but I took advantage of ApacheCon 2008 by having Martijn Dashorst sign my personal copy of Wicket in Action. Fortunately Bruno Borges was on-hand to document the momentous occasion!
Wicket QuickStart Tutorial
So, you posted something to the Wicket mailing list saying that you thought you found a bug or you had a problem and were told to “create a quickstart” duplicating the problem. And then you said “how”? There are two ways and each will be described here:
Read the rest of this entry »
Meet the Wicket Community - Little ol’ Me!
After a great week at ApacheCon last week, it was an extra privilege to spend the time with Martijn Dashorst and Bruno Borges. An added privilege was the opportunity to complete my interview with Martijn in person at ApacheCon.
To read more about me and my Wicket experiences, check out his interview with me at: wicketinaction.com/2008/11/meet-the-wicket-community-jeremy-thomerson/
ApacheCon - Java Monitoring and Troubleshooting Tools in Action
Presented by Bill Au, of the Platform Infrastructure group at CNET
Bill is going to help us learn about how to troubleshoot and monitor java apps, thread and heap dumps, hung or slow apps, OutOfMemoryErrors, and JVM crashes. All of the tools he is going to show us are free tools - open source or free for download.
NOTE: This was a very interesting session. One of the things I was impressed with was his demonstrations of some tools that I have not seen. There was the HP JMeter tool, an open source tool called Samurai, and a perl script that he wrote. All of them look very helpful, and I want to try them all out (not that I have every written any apps that ever have performance issues - but I’m sure I can help someone else look at theirs!)
Read the rest of this entry »
ApacheCon - Guidelines and Best Practices - System Architecture of Web Applications
Presented by Ravi Saraswathiamma, architect with AOL / Time-Warner
When setting up an application, you have to identify hardware / software / networking / infrastructure architecture. How do you do this? The first step is of course gathering the requirements - what is required? What kind of application is it? Do you need HTTPS, etc. What are the best practices?
Read the rest of this entry »