Thanks for the help Frank. The changes you mentioned solved my problem. I was operating under the fallacious assumption that the Page object was attached to the <body> tag.
Now, regarding the following: "getBodyContainer().getBodyContainer() returns the WebMarkupContainer which corresponds with the <body> tag. (Though I don't know how good the support is for having javascript events on the <body> tag in the different browsers)" I noticed that the Wicket Developers have a "TODO" item for changing the name of "BodyContainer" to something else as it is really just a facade used for getting what the user of the API would want, a reference to the WebMarkupContainer, which is exactly what I am doing here. Maybe they could even go so far as to add a "getWebMarkupContainer()" to the WebPage class. I think this would be less verbose and communicate the intent of the code more clearly. Finally, I was wondering if there is any way to actually look at what key was pressed that triggered the JS "onkeypressed" event from the perspective of the API. I hunted through the AjaxRequestTarget class and I could not find a way to get this particular information or anything else regarding the event. Does Wicket expose this somehow? Thanks again for your advice. -MT ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
