You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Tapani Saarinen (JIRA)" <ji...@apache.org> on 2011/04/08 17:17:05 UTC
[jira] [Created] (WICKET-3604) Filter path not set in WicketFilter
Filter path not set in WicketFilter
-----------------------------------
Key: WICKET-3604
URL: https://issues.apache.org/jira/browse/WICKET-3604
Project: Wicket
Issue Type: Bug
Components: wicket-core
Affects Versions: 1.5-RC3
Environment: Jetty embedded
Reporter: Tapani Saarinen
Priority: Blocker
This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
CODE:
FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
context.addFilter(filterHolder, "/*", 1);
LOG:
Starting Jetty server...
WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3604) Filter path not set in
WicketFilter
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017489#comment-13017489 ]
Igor Vaynberg commented on WICKET-3604:
---------------------------------------
i dont see how 1.4 could figure out the path in this environment unless you explicitly set it before using setInitParameter. please provide a quickstart for 1.4.x where this works so we can figure out which code we lost.
> Filter path not set in WicketFilter
> -----------------------------------
>
> Key: WICKET-3604
> URL: https://issues.apache.org/jira/browse/WICKET-3604
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: Jetty embedded
> Reporter: Tapani Saarinen
> Priority: Minor
>
> This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
> CODE:
> FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
> filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
> context.addFilter(filterHolder, "/*", 1);
> LOG:
> Starting Jetty server...
> WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
> Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3604) Filter path not set in
WicketFilter
Posted by "Tapani Saarinen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017622#comment-13017622 ]
Tapani Saarinen commented on WICKET-3604:
-----------------------------------------
This way it works, but what point is there to set the mapping twice? FilterHolder should get the mapping from Jetty when addFilter is called.
filterHolder.setInitParameter(WicketFilter.FILTER_MAPPING_PARAM,"/*");
context.addFilter(filterHolder, "/*", 0);
> Filter path not set in WicketFilter
> -----------------------------------
>
> Key: WICKET-3604
> URL: https://issues.apache.org/jira/browse/WICKET-3604
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: Jetty embedded
> Reporter: Tapani Saarinen
> Priority: Minor
>
> This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
> CODE:
> FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
> filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
> context.addFilter(filterHolder, "/*", 1);
> LOG:
> Starting Jetty server...
> WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
> Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-3604) Filter path not set in
WicketFilter
Posted by "Tapani Saarinen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017615#comment-13017615 ]
Tapani Saarinen commented on WICKET-3604:
-----------------------------------------
The actual path is provided with mountPage in WebApplications init method. Filter just enables Wicket to handle the mounts. I don't know if it's WicketFilter or the mounting, which does not work. It worked in 1.5-M3, though the mountPage was changed from 1.4 to something getXXXX.add() and now again to mountPage.
mountPage("/status", Status.class);
> Filter path not set in WicketFilter
> -----------------------------------
>
> Key: WICKET-3604
> URL: https://issues.apache.org/jira/browse/WICKET-3604
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: Jetty embedded
> Reporter: Tapani Saarinen
> Priority: Minor
>
> This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
> CODE:
> FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
> filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
> context.addFilter(filterHolder, "/*", 1);
> LOG:
> Starting Jetty server...
> WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
> Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (WICKET-3604) Filter path not set in WicketFilter
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-3604.
-------------------------------------
Resolution: Not A Problem
This is needed for Wicket internal needs.
> Filter path not set in WicketFilter
> -----------------------------------
>
> Key: WICKET-3604
> URL: https://issues.apache.org/jira/browse/WICKET-3604
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: Jetty embedded
> Reporter: Tapani Saarinen
> Priority: Minor
>
> This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
> CODE:
> FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
> filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
> context.addFilter(filterHolder, "/*", 1);
> LOG:
> Starting Jetty server...
> WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
> Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (WICKET-3604) Filter path not set in WicketFilter
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg updated WICKET-3604:
----------------------------------
Priority: Minor (was: Blocker)
> Filter path not set in WicketFilter
> -----------------------------------
>
> Key: WICKET-3604
> URL: https://issues.apache.org/jira/browse/WICKET-3604
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC3
> Environment: Jetty embedded
> Reporter: Tapani Saarinen
> Priority: Minor
>
> This does not work anymore. Worked in 1.4.x and 1.5.M3. I use Jetty in embedded mode with NO xml configuration files. So I initialize all servlets and filters in code.
> CODE:
> FilterHolder filterHolder = new FilterHolder(WicketFilter.class);
> filterHolder.setInitParameter(ContextParamWebApplicationFactory.APP_CLASS_PARAM, XXXXX.MainApplication.class.getName());
> context.addFilter(filterHolder, "/*", 1);
> LOG:
> Starting Jetty server...
> WicketFilter [WARN] Unable to determine filter path from filter init-parm, web.xml, or servlet 3.0 annotations. Assuming user will set filter path manually by calling setFilterPath(String)
> Application [INFO] [org.apache.wicket.protocol.http.WicketFilter-324750153] init: Wicket core library initializer
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira