Ai. Yeah, that's a common one. I wonder if there is any way we can check at startup whether package resources are available to clients. The only thing I can think of is to issue an HTTP request to localhost to retrieve a shared resource, and test whether this does give the expected result. Wonder if that's doable without too many headaches.
Eelco On 3/17/06, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote: > > To all Wicket Users that may be having Javascript errors indicating 'Object > Expected' from browser most times..please after you have done what you are > expected to do..perform this simple check: > > Look into your Web.xml and confirm that the context reference of the > WicketServlet is /app/* and not /app > > this gave me a lot of problems with all Ajax functionality in Wicket so dont > fall into my former pit :) > > Thanks ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
