Thanks, I fixed some of the problems of the persistent :) Those new pages, really need to be persistent, it is the user login that is being held on the session ;)
Thanks for the help, I really need a break, today I've worked 11 hours, and i got stuck three hours trying to deal with a problem with xmlhttprequest, the problem was right before my eyes, after taking a short break for a snack I found that I was using setTimeout() function in the wrong place and that was crashing the browser :P I really would like to use 4.1 but I'm kinda short on time and I have not fixed the whole oc4j problem yet :( Regards On 8/22/06, hv @ Fashion Content <[EMAIL PROTECTED]> wrote:
I would bet on Tap4.1(currently alpha) if I was in your shoes when it comes to Ajax. 1) The Tap4 part is likely to be fairly stable. 2) The Ajax part is based on Jesses prior work on Tacos 3) It seems to be progressing at a fast pace. I don't know your application, but I would get the non session dependent pages working first. If I remember correctly you were having some mixup earlier with where to access property values and tried to fix it by making the property persistent. I would strongly recommend making a sandbox webapp and play around with the callbacks/listeners until you understand the when & why. There is quite a bit of Tapestry documentation and in this case the old Tap3 user guide isn't a bad starting point. Henrik "Vinicius Carvalho" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > Working 12 hours a day, 7 days a week, under heavy pressure makes you > do stupid things (but as Scott Adams says, every one is stupid). > > Sorry folks, was so desperate to get help that did not noticed what > was happening: > > For my 3 problems: > > The number of Httpsessions and the number of invocations, seems to be > close related to the fact that I was debugging the app, even with no > breakpoint set, Have no idea why, but as soon as I started tomcat with > jpda off, things come back to normality > > The crash, is happening because of javascript, I have no idea why, > since I've tested it on a blank app, I suck on JS big time, but I'll > seek for another resource (its an ugly NS_EXCEPTION) read something > about xmlrequest being already opened and such, this one I'd love to > have some help from the masters of dojo/js/ajax here :P > > Best regards and sorry for the spam :P > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
