Regarding the debugging: Debugging is very easy in Wicket since most of the meat is in Java (instead of tags). What do you mean by setting breakpoints in templates? I assume that it 'might' be possible to debug the component tag rendering process, but then one would have to skip the jars and load Wicket as a source module.
In general, Wicket does a great job of giving your trace output of your template when something goes awry, including the component inheritance and suggestions as to what could be wrong. Regarding loading remote templates - wouldn't that be a potential security concern and be prevented by the underlying app server? Michael -----Original Message----- From: mraible [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 5:09 PM To: [email protected] Subject: A few Wicket Questions 1. Is it possible to load templates from a remote server/url/jar? 2. Is it possible to set breakpoints in templates and debug them using an IDE? 3. Does Wicket have any support for REST? 4. Does Wicket declare OSGi meta-data in its JARs? 5. Can I write a Wicket application that spans several WARs and has the ability to navigate from one WAR to the next (essentially have a central URL mechanism)? Most Wicket apps I've seen require page classes in the classpath to navigate from one page to the next. 6. Is there any support for component degradation, where you can disable a component at runtime (to compensate for high-load and such)? Thanks, Matt -- View this message in context: http://www.nabble.com/A-few-Wicket-Questions-tp16576719p16576719.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
