it should be just fine to funnel your jsps into wicket. wicketfilter
checks if the request is for wicket or not and if not lets the servlet
container handle it...thats why its now a filter and not a servlet...

-igor


On Wed, Mar 12, 2008 at 11:10 AM, Sri Sankaran <[EMAIL PROTECTED]> wrote:
>
>  I would like to include a couple of utility JSP s along with my otherwise
>  Wicket-ized application.  However, I don't know how to instruct the Wicket
>  Filter to only handle HTML pages? I want the container (WebLogic) to handle
>  the JSPs.  My first attempt was:
>
>
>     &lt;filter-mapping>
>         &lt;filter-name>wicket_filter&lt;/filter-name>
>         &lt;url-pattern>/*.html&lt;/url-pattern>
>     &lt;/filter-mapping>
>
>
>  I struck out with the stack trace:
>
>
>  java.lang.IllegalArgumentException:  for WicketFilter "wicket_eval_filter"
>  must start with '/' and end with '*'.
>         at
>  
> org.apache.wicket.protocol.http.WicketFilter.getFilterPath(WicketFilter.java:693)
>         at
>  org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:472)
>  etc
>
>
>  I checked the logic of WicketFilter and was incredulous to see
>
>
>  if (!urlPattern.startsWith("/") || !urlPattern.endsWith("*")) {
>   // throw the exception
>  }
>
>
>  Why?  Is that a requirement of the servlet spec? I think not.  Why have a
>  mapping element if it is forced to be of the form /*?
>
>  More importantly, how can I make sure that my JSP doesn't get funnelled to
>  the WicketFilter?
>
>  Sri
>  --
>  View this message in context: 
> http://www.nabble.com/Direct-only-*.html-to-Wicket-Filter-tp16011111p16011111.html
>  Sent from the Wicket - User mailing list archive at Nabble.com.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to