Marin� A. J�nsson said: ... > > > 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).
i suspect this will be a key to finding the bug. if you can identify the suffering component, strip the content to the others to a minimum, and change the template/content for that component to something that clearly tests/indicates what is available in that context and what is not, then that would help a lot. > > > 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) well, given that it went away, i have to wonder if it isn't some sort of session/initialization type problem. does the app make much use of sessions? are there any session scoped tools? with so few concurrent users i can't believe it would be any sort of load problem. i suppose it could be some sort of concurrency problem (due to the seven near-simultaneous requests (thru the request dispatcher) to the VVS, but even there i'm still a bit skeptical. ... > > > 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. ... well, there may not be many other ways to find the bug. and for fixing it and confirming the fix, being able to narrow things down to a simple test case is critical. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
