Marin� A. J�nsson said: > I just came across the weirdest behaviour. > I use the TilesTool to assemble pages from page components.
ok, but i'm not sure i understand the problem/situation. so i'm reorganizing the info below to get clarification. and if i've misunderstood anything, please correct me. > 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 is the app just running on one server or are these guys running it locally? is this your server setup? or their local setup? > I made the web-app accessible online to a client and > immediately...one component in one page didn't render correctly. is it always the same component in the same page? or the same component in different pages? or different components in the same page? > another guy on an apple computer didn't have any trouble. > third guy (on another windows box) had the same trouble as the first so, are these three guys are just pointing their browser to it and getting different results based on browser/OS being used? are the results for these different guys consistent? are there any other factors different between them? (e.g. different logins/accounts?) and i'm on a windows box. if you wanna privately send me a url to see the prob for myself, i'd be happy to take a look. > after browsing for a while, the problem silently went away > I found no error messages in the logs ugh. damn sneaky bugs. can he/they recreate the problem again? by relogging in or restarting browser or clearing cache or cookies or anything? > I couldn't reproduce the bug on my workstation again, pointing to the app on a server or just running locally on the workstation? > 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. can you try stripping down a version of the app to test this theory? it might help narrow down the problem. > 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? nope, i'm clueless at this point. and i'm still not even really sure what "this" is. :) Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
