> 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'm running the server from my workstation. > > 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? at least the same component in different pages - I didn't get a chance to test it myself (I'm going to have a more rigorous session with them tomorrow). > > 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?) yes, they are only pointing their browsers to it and apparently getting different results, but I'm not sure it has anything to do with browser/OS (since the bug doesn't appear consistently on IE/Win - for the first guy the bug went away after the first few minutes) > 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. cool :) ... I'll send the URL in a private mail in a minute. > > 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? they didn't have to log in or anything - just fire up and browse. The bug didn't reappear for the first guy after it went away. All the info I have right now is based on these three phonecalls and the single screenshot. I'll know more tomorrow. > > I couldn't reproduce the bug on my workstation > > again, pointing to the app on a server or just running > locally on the workstation? 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. the app is pretty compact so I'm not sure that would help much ... we'll see. > > 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. :) heh heh ... hope you have a better idea now :) Marin� --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
