About (2)
can you try throwing a PageRedirectException ( instead of
cycle.activate("Login") )
to see if tacos intercepts and handles this correctly?(1) can very well be a bug... I think i've read some similar complains with normal Tapestry Exception pages, but i'll have to dig into it more Holger Stolzenberg wrote: > Sorry for the interupted previous message, something hit my keyboard! > > Hello everyone out there! I have two problems and I actually have no > idea what to do against it. I am using tap4.0.2 with tacos 4.0.0. > > (1) AjaxExceptionPresenter > > I am using a custom AjaxExceptionPresenter, which I declared in > hivemodule.xml: > > <implementation service-id="tacos.AjaxExceptionPresenter"> > <invoke-factory> > <construct > class="com.ewerk.zuebee.util.AjaxExceptionPresenter"> > <set property="exceptionPageName" > value="CustomException"/> > </construct> > </invoke-factory> > </implementation> > > The presenter gets called and redirects to the ExceptionPage. The > problem is that the output rendered by this ExceptionPage is not UTF-8, > it is rendered as ISO-8859-1. I think that I already have done > everything to ensure UTF-8 output. Every other page in my app is > rendered correctly. The ExceptionPage is also rendered correctly if it > was not called by the custom AjaxExceptionPresenter. > > > (2) Broken AJAX response > > My app is fully ajax enabled using Tacos tree, AjaxDirectLinks and so > on. All my pages implement the pageValidate() method in which I > implement login logic. When I click on an AjaxDirectLink the request is > sent to the server, so pageValidate() gets called. When pageValidate() > fails (session expired, something else wrong) i am redirecting the user > to the login page via cycle.activate( "Login" ). > > Now the problem. > > I my log output I can see that the login page gets rendered, but nothing > happens in the browser, that means nothing is updated. The AJAX response > that has been logged in the DebugConsole is no real AJAX response, it is > the complete response-source code for the login page (<html> ..... > </html>). I have no clue what is happening there and I have no time to > deep dig in Tacos and Dojo. > > Whereas issue (1) is only a minor, issue (2) is a really great problem > because it directly breaks application workflow. > > > Anyone any ideas :-( > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Tacos-devel mailing list > Tacos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tacos-devel > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel
