On Tue, 08 Apr 2008 17:29:16 -0700, Michael Mehrle wrote:
> 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.
And for that I am *very* thankful. I've only ju
> not out of the box. ISecurityStrategy does provide a central point to
> intercept lifecycle event, so you can easily do something like
>
> new isecuritystrategy() { boolean isactionallowed(component caction a) {
> if (pastLoadThreshold()&&component.render.equals(a)&&c instanceof
> degradabl
On Tue, Apr 8, 2008 at 5:08 PM, mraible <[EMAIL PROTECTED]> wrote:
>
> 1. Is it possible to load templates from a remote server/url/jar?
yes. you will have to roll your own IResourceStreamLocator
> 2. Is it possible to set breakpoints in templates and debug them using an
> IDE?
no. but why wo
Michael Mehrle wrote:
>
> 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 o
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
