The stack trace and error page should provide enough information to figure that out. Can you find it and send it as a reply?
All logging in Wicket goes via commons logging usually using the class name for loggers. Most people will probably use Log4J as the implementation, which means you can turn it on like: log4j.logger.wicket=DEBUG and/ or log4j.logger.wicket.protocol.http.WebSession=DEBUG in e.g. log4j.properties in your classpath root. See for more info the respective logging package you are using and commons logging documentation. Eelco On 11/27/05, Pekka Henttonen <[EMAIL PROTECTED]> wrote: > > A simple question from a newbie: how can you find out what tag is expected > when you get a "wicket.markup.MarkupException: Tag expected" -error. How > do you turn debugging on? > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
