You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Commented) (JIRA)" <ji...@apache.org> on 2012/01/02 08:50:32 UTC
[jira] [Commented] (WICKET-4303) mounting a home page with package
mapper results in invalid url's
[ https://issues.apache.org/jira/browse/WICKET-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178316#comment-13178316 ]
Martin Grigorov commented on WICKET-4303:
-----------------------------------------
@Peter: can this fix be ported to 1.5 ?
> mounting a home page with package mapper results in invalid url's
> -----------------------------------------------------------------
>
> Key: WICKET-4303
> URL: https://issues.apache.org/jira/browse/WICKET-4303
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.3, 6.0.0
> Environment: Internet Explorer,Chrome (Probably occurs in any browser)
> Reporter: Masaya Seko
> Assignee: Peter Ertl
> Labels: wicket
> Attachments: WICKET-4303WithWicket6.0.zip, screenshot-1.jpg, wicket153mount.zip
>
>
> If the transition destination page mountPackage HomePage, which displays a 404 error when you click on the link the normal component.
> This would not be a bug?
> When you reload before click, the issue does not occur.
> Wicket 1.4 this issue does not happen.
> The stack trace below.
> WARN - WicketObjects - Could not resolve class [wicket153mount...]
> java.lang.ClassNotFoundException: wicket153mount///
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:242)
> at org.apache.wicket.application.AbstractClassResolver.resolveClass(AbstractClassResolver.java:108)
> at org.apache.wicket.util.lang.WicketObjects.resolveClass(WicketObjects.java:68)
> at org.apache.wicket.request.mapper.AbstractComponentMapper.getPageClass(AbstractComponentMapper.java:138)
> at org.apache.wicket.request.mapper.PackageMapper.parseRequest(PackageMapper.java:142)
> at org.apache.wicket.request.mapper.AbstractBookmarkableMapper.mapRequest(AbstractBookmarkableMapper.java:263)
> at org.apache.wicket.request.mapper.mount.UnmountedMapperAdapter.mapRequest(UnmountedMapperAdapter.java:73)
> at org.apache.wicket.request.mapper.mount.MountMapper.mapRequest(MountMapper.java:131)
> at org.apache.wicket.request.mapper.CompoundRequestMapper.mapRequest(CompoundRequestMapper.java:130)
> at org.apache.wicket.request.cycle.RequestCycle.resolveRequestHandler(RequestCycle.java:181)
> at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:206)
> at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:280)
> at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:162)
> at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:218)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira