Re: Wicket-spring-tomcat integration

2008-12-15 Thread Richard Allen
The url-pattern only supports using a wildcard at the end of the pattern
(e.g., "/myapp/*") or as a extension mapping prefix (e.g., *.do). See
section SRV.11.2 of the servlet specification, which can be downloaded from
here:
http://jcp.org/aboutJava/communityprocess/final/jsr154/index.html

Therefore, I believe the closest you could do would be

WicketFilter
/a/*

...

WicketFilter
/b/*

If that doesn't suit your needs, you might need to extend WicketFilter with
a custom implementation.


On Mon, Dec 15, 2008 at 3:11 AM, Arie Fishler  wrote:

> Hi,
>
> I am using wicket via tomcat integrated into spring using a filter with *
>
> org*.*apache*.*wicket*.protocol.*http*.WicketFilter
>
> The thing is that I want to map the wicket application to several url
> patterns (to know which environment the user is coming from)
>
>
>
> Is there a way to map the filter to several patterns? like the below which
> does not work...
>
> 
>
> WicketFilter
>
> /*a*/*
>
> 
>
> and
>
> 
>
> WicketFilter
>
> /*b*/*
>
> 
>


Wicket-spring-tomcat integration

2008-12-15 Thread Arie Fishler
Hi,

I am using wicket via tomcat integrated into spring using a filter with *

org*.*apache*.*wicket*.protocol.*http*.WicketFilter

The thing is that I want to map the wicket application to several url
patterns (to know which environment the user is coming from)



Is there a way to map the filter to several patterns? like the below which
does not work...



WicketFilter

/*a*/*



and



WicketFilter

/*b*/*