I know this would be very difficult to create by hand, but if you
automatically create a web.xml which includes 200 such filter
definitions (replacing Application1 and dbfile1 with other values) I
think that would do what you want. Note that here you obtain the db
configuration file name as a filter init parameter, you should modify
your application's init method accordingly..
<filter>
<filter-name>Application1</filter-name>
<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
<init-param>
<param-name>applicationClassName</param-name>
<param-value>com.mycompany.MyApplication</param-value>
</init-param>
<init-param>
<param-name>dbFileName</param-name>
<param-value>dbfile1.properties</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>Application1</filter-name>
<url-pattern>/dbfile1/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
Sean W wrote:
path:
/ContextPath/wicket/BookmarkablePage
It appears to me that using Wicket you cannot place anything in the path
between the context path and the mounted name except for "wicket", which is
defined as your <url-pattern>. In other words, a mounted page cannot be
referenced from more than one path. This also means Wicket can't support
"sub contexts".
Perhaps I'll have to try and deploy a single app 200 times in tomcat with
the same WAR. :-S
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
