Hi.
On Thu, Nov 29, 2012 at 1:52 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> Hi,
>
> On Thu, Nov 29, 2012 at 1:38 PM, Karsten Gaul wrote:
>
>> Hi Ernesto,
>>
>> Thanks but this isn't really what I was looking for as it is too simple
>> to remove the Modal Window from the DOM tree
Hi,
On Thu, Nov 29, 2012 at 1:38 PM, Karsten Gaul wrote:
> Hi Ernesto,
>
> Thanks but this isn't really what I was looking for as it is too simple to
> remove the Modal Window from the DOM tree and see the already rendered
> hidden page without entering a PIN.
>
> Don't put the hidden content til
Hi Ernesto,
Thanks but this isn't really what I was looking for as it is too simple
to remove the Modal Window from the DOM tree and see the already
rendered hidden page without entering a PIN.
I'd use normal Modal Windows for every link to the PIN protected page
but this wouldn't cover book
See
https://cwiki.apache.org/confluence/display/WICKET/Modal+Windows
Opening a modal window on page load (no AJAX involved)
You could use one to "block" the page till pin is typed.
On Wed, Nov 28, 2012 at 1:29 PM, Karsten Gaul wrote:
> Hi everyone,
>
> I'm currently building an application us
Hi everyone,
I'm currently building an application using wicket 1.4.21 and what I'm
trying to achieve is the following:
I have a protected area (stage 1) which requires the user to input his
credentials and I'm using an AuthorizationStrategy for this. This
Strategy throws a RestartResponseAt
