Hi guys, I just came across the weirdest behaviour.
I am developing an online store and I use the TilesTool to assemble pages from page components. I made the web-app accessible online to a client and he immediately complained that one of the page components in one of the pages didn't render correctly. Since I couldn't reproduce the bug on my workstation and I found no error messages in the logs, he sent me a screenshot. Then, after he had browsed the web-app for a while, the problem silently went away and all was well. I got another guy to try it out - on an apple computer - and he didn't have any trouble. The third guy however (on another windows box) had the same trouble as the first guy. It seems each of the page components gets imported ok - but for (at least) one component none of the standard contexts (i.e. request, session, or toolbox) are accessible. Many of the page components have their own controller bean that populates them with data (using request or session scope). Since TilesTool uses a RequestDispatcher to include resources each page component has it's own Velocity context. Which brings me to VelocityViewServlet and the ChainedContext ... the page definition in question contains six components - so counting the layout page it makes seven, almost simultaneous, calls to VelocityViewServlet for each page. I took a look for myself but I couln't find anything that could shed any light on this behaviour. Any idea what could possibly be causing this? Velocity 1.5-dev Velocity Tools 1.2-dev Struts 1.2-dev Tomcat 4.1.29 & Tomcat 4.1.30 JDK 1.4.2 WinXP cheers, Marino --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
