[
https://issues.apache.org/jira/browse/WICKET-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444838#comment-13444838
]
Jesse Long commented on WICKET-4737:
------------------------------------
Doesn't matter, why take away a nice feature when there is no need to? Right
now, setFilterPath() is useless to anyone except WicketFilter.init(). Either it
must work, or it should be removed.
I'll use init params to work around in the mean time, but I like the feature
and I'd like it to work again in 6.0.1.
> IllegalStateException on WicketFilter.init() after calling setFilterPath()
> --------------------------------------------------------------------------
>
> Key: WICKET-4737
> URL: https://issues.apache.org/jira/browse/WICKET-4737
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0
> Environment: When you pre-configure the filter path using the
> setFilterPath() method.
> Reporter: Jesse Long
> Attachments: WICKET-4737.patch
>
>
> WICKET-4626 broke the ability to pre-set the filter path using
> setFilterPath(). The patch introduced by WICKET-4626 calls setFilterPath()
> from within WicketFilter.init(), and setFilterPath() throws
> IllegalStateException if it is called more than once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
