you can by subclassing it...
-igor
On Mon, Jul 19, 2010 at 10:50 AM, Erik van Oosten wrote:
> Presumably because you can not configure the wicket filter through code?
>
> I agree. The use case is thin.
>
> Regards,
> Erik.
>
>
> Op 19-07-10 18:24, Igor Vaynberg wrote:
>>
>> why do we need thi
Presumably because you can not configure the wicket filter through code?
I agree. The use case is thin.
Regards,
Erik.
Op 19-07-10 18:24, Igor Vaynberg wrote:
why do we need this? afaik in 1.4 wicket filter can be configured to
ignore paths
-igor
--
Sent from my SMTP compliant sof
The Wicket team is happy to announce that Martin Grigorov was invited to
join the Wicket team as a committer and PMC member, and he accepted!
Martin's relentless patience, high quality patches and sustained
energy haven't gone unnoticed. He has continually provided valuable
insights and put a lot
why do we need this? afaik in 1.4 wicket filter can be configured to
ignore paths
-igor
On Mon, Jul 19, 2010 at 8:49 AM, Martin Grigorov wrote:
> Hi,
>
> A have a Wicket 1.5 question:
>
> There is a comment
> in org.apache.wicket.protocol.http.WebApplication.addIgnoreMountPath(String)
> :
> publ
Hi,
A have a Wicket 1.5 question:
There is a comment
in org.apache.wicket.protocol.http.WebApplication.addIgnoreMountPath(String)
:
public final void addIgnoreMountPath(String path)
{
// TODO how is this supposed to work :/
throw new UnsupportedOperationException();
}
Idea:
currently the root ma
