click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLK-424) not using ".htm" extension cause click to go on loop
Date Sat, 19 Jun 2010 15:02:23 GMT

    [ https://issues.apache.org/jira/browse/CLK-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880491#action_12880491
] 

Bob Schellink commented on CLK-424:
-----------------------------------

Yes, the idea was to use URL and templates with ".xml" instead of ".htm". I think this issue
was largely fixed by https://issues.apache.org/jira/browse/CLK-568.

I don't use Click with alternate extensions so not sure how well this works in practice.

> not using ".htm" extension cause click to go on loop
> ----------------------------------------------------
>
>                 Key: CLK-424
>                 URL: https://issues.apache.org/jira/browse/CLK-424
>             Project: Click
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.5 M3
>         Environment: Gentoo Linux, OpenSolaris, Solaris 9 for sparc. Using both Glassfish
and Bea Weblogic
>            Reporter: Stefax
>         Attachments: click_framework_and_xml.pdf
>
>
> In click documentation I don't find a "must" in using the ".htm" extension for my pages.
So I decided to add my own Controllers and Container to handle a different language XML based,
allowing me using the Page to generate xml like pages. For this I use the ".vxml" extension,
but when I tryed to launch my page it failed to render due to a click loop in generating an
infinite time the code for the page....
> javax.servlet.ServletException: PWC1232: Exceeded maximum depth for nested request dispatches:
20
>         at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:842)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:703)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:542)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:474)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:366)
>         at net.sf.click.ClickServlet.processPage(ClickServlet.java:661)
>         at net.sf.click.ClickServlet.handleRequest(ClickServlet.java:331)
>         at net.sf.click.ClickServlet.doGet(ClickServlet.java:250)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
>         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
>         at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:855)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:703)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:542)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:474)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:366)
>         at net.sf.click.ClickServlet.processPage(ClickServlet.java:661)
>         at net.sf.click.ClickServlet.handleRequest(ClickServlet.java:331)
>         at net.sf.click.ClickServlet.doGet(ClickServlet.java:250)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
>         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
>         at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:855)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:703)
>         at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:542)
>         at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:474)
>         at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:366)
>         at net.sf.click.ClickServlet.processPage(ClickServlet.java:661)
>         at net.sf.click.ClickServlet.handleRequest(ClickServlet.java:331)
>         at net.sf.click.ClickServlet.doGet(ClickServlet.java:250)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
>         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
>         at org.apache.catalina.core.ApplicationDispatcher.doInvoke(ApplicationDispatcher.java:855)
>         at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:703)
>         .....
> I think that it would be good to handle this exception or not allowing click to go on
loop, but simply writing an error message saying "Extension not supported" or something like
this. I also think that is useful to allow click to manage any type of extensions.
> Can you please help me giving me a suggestion on how to permit click to render my page
whithout going on loop? I'm reading the click source code, but if you can tell me what methods
to override, my work will be faster and precise.
> Thanks

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message