Re: Weird Javascript error in continuations
Toby wrote: Leszek wrote: Simply speaking: page local is a special variable that has different values in different continuations. So it seems that a continuation by default only saves the "program counter" (or equivalent notion in JS) but not the local variables. This is a bit counter-intuit
Re: Weird Javascript error in continuations
> Leszek wrote: >> Simply speaking: page local is a special variable that has different >> values in different continuations. > > So it seems that a continuation by default only saves the "program > counter" (or equivalent notion in JS) but not the local variables. > This is a bit counter-intuitive
Re: Weird Javascript error in continuations
Leszek wrote: > Simply speaking: page local is a special variable that has different > values in different continuations. So it seems that a continuation by default only saves the "program counter" (or equivalent notion in JS) but not the local variables. This is a bit counter-intuitive, and bla
RE: Weird Javascript error in continuations
Thx Mark and Leszek, very enlightning! Might be worth documenting a little :-) > > Mark Lundquist wrote: > > > > On Aug 1, 2006, at 1:07 AM, Ard Schrijvers wrote: > > > >> I never used (saw :-) ) this createPageLocal untill now, > > > > Huh, I sent a reply on this thread suggesting > create
Re: Weird Javascript error in continuations
On Aug 1, 2006, at 1:38 PM, Leszek Gawron wrote: Of course if state was declared like this: var state = {} so an "ordinary" variable then if the first continuation is reinvoked the state.step will have the 'Step 2' value. Quite so... thanks for amplifying my example. BTW, resource conside
Re: Weird Javascript error in continuations
Mark Lundquist wrote: On Aug 1, 2006, at 1:07 AM, Ard Schrijvers wrote: I never used (saw :-) ) this createPageLocal untill now, Huh, I sent a reply on this thread suggesting createPageLocal() last week, oh well... :-) and looked at http://cocoon.apache.org/2.1/userdocs/flow/api.html, but
Re: Weird Javascript error in continuations
On Aug 1, 2006, at 1:07 AM, Ard Schrijvers wrote: I never used (saw :-) ) this createPageLocal untill now, Huh, I sent a reply on this thread suggesting createPageLocal() last week, oh well... :-) and looked at http://cocoon.apache.org/2.1/userdocs/flow/api.html, but I don't really get th
RE: Weird Javascript error in continuations
> > Continuations are for managing flow, not keeping full state > because it > would consume too much resources. In 99% you do not need variables to > have values bound to a specific continuation. Still you have > an option > to do so: > > var pageLocal = cocoon.createPageLocal(); > pageLoc
Re: Weird Javascript error in continuations
Simone Gianni wrote: Hi Toby, I think you are right. What a continuation does (should do) is dump the local variables and restore them before restarting the flow. This means that if you write var a = 1; then create a continuation, when you return to that continuation a should be 1 again, even if
RE: Weird Javascript error in continuations
Hello Simone, talking about continuations, did you already find a solid way to handle high traffic sites with many concurrent continuations and memory useage? It bothers me a little that when building sites, we have to keep track of the number of continuations (we had a large site with many vis
Re: Weird Javascript error in continuations
Hi Toby, I think you are right. What a continuation does (should do) is dump the local variables and restore them before restarting the flow. This means that if you write var a = 1; then create a continuation, when you return to that continuation a should be 1 again, even if in other continuations
Re: Weird Javascript error in continuations
Jason Johnston wrote: > First you assign the 'useless' variable a String value, then you > create the continuation. When you resume the continuation the first > time, you re-assign the 'useless' variable so that it now holds an > Array value (String.split() returns an Array). When you resume the
Re: Weird Javascript error in continuations
On Jul 25, 2006, at 7:34 AM, Toby wrote: I just came across a very strange error, possibly a bug in Cocoon! Nope, as Jason explained, this is the correct behavior. The cocoon.createPageLocal() method might help you, see here: http://cocoon.apache.org/2.1/userdocs/flow/api.html —ml—
Re: Weird Javascript error in continuations
Jason Johnston wrote: > First you assign the 'useless' variable a String value, then you > create the continuation. When you resume the continuation the first > time, you re-assign the 'useless' variable so that it now holds an > Array value (String.split() returns an Array). When you resume the
Re: Weird Javascript error in continuations
> I just came across a very strange error, possibly a bug in Cocoon! > > It's easy to reproduce: edit samples/blocks/forms/flow/registration.js > from Cocoon 2.1.8, adding the lines marked with '>' > > > function registration() { >> var useless = 'one two'; > var form = new Form("forms/regist
Weird Javascript error in continuations
I just came across a very strange error, possibly a bug in Cocoon! It's easy to reproduce: edit samples/blocks/forms/flow/registration.js from Cocoon 2.1.8, adding the lines marked with '>' function registration() { > var useless = 'one two'; var form = new Form("forms/registration.xml");
AW: [cocoon forms] Javascript error
f: RE: [cocoon forms] Javascript error > > > Hi Helma, > > The error actually happens after the form is > submitted, so I would imagine, the control is passed > back to the flowscript. It seems like the error is > coming from: > > resource://org/apache/cocoon/woody/flow/javasc
RE: [cocoon forms] Javascript error
Hi Alex, > Are you using the provided woody stylesheets right > from the cocoon directory or do you copy them into > your own application? I copied them to my own application and modified them slightly. Most modifications are display related, but I added an extra test to skip the entire addition
RE: [cocoon forms] Javascript error
t; woody-block.jar (or similar > name) for examination. And it's available in the > source tree of your cocoon > repository. > > Bye, Helma > > > -Original Message- > > From: Alex Romayev [mailto:[EMAIL PROTECTED] > > Sent: Monday, 05 January 200
RE: [cocoon forms] Javascript error
OTECTED] > Sent: Monday, 05 January 2004 22:08 > To: [EMAIL PROTECTED] > Subject: RE: [cocoon forms] Javascript error > > > Hi Helma, > > The error actually happens after the form is > submitted, so I would imagine, the control is passed > back to the flowscr
RE: [cocoon forms] Javascript error
day, 05 January 2004 19:08 > > To: [EMAIL PROTECTED] > > Subject: [cocoon forms] Javascript error > > > > > > Hi, > > > > I'm getting a Javascript error when I submit my > form. > > The functionality works fine, except for this > error >
RE: [cocoon forms] Javascript error
er error I came across: I added an action to my form that was not related to any sitemap pattern. Bye, Helma > -Original Message- > From: Alex Romayev [mailto:[EMAIL PROTECTED] > Sent: Monday, 05 January 2004 19:08 > To: [EMAIL PROTECTED] > Subject: [cocoon forms] Ja
[cocoon forms] Javascript error
Hi, I'm getting a Javascript error when I submit my form. The functionality works fine, except for this error briefly comes up while the browser is openning the next page. Any idea why it's happening? Here is the error: Line: 44 Char: 1 Error: Object expected Code: 0 Java
Re: Javascript Error
Try: // (You should also use type="text/javascript" rather than the depricated language attribute. See http://www.w3schools.com/tags/tag_script.asp) - Justin On 9/18/03 9:01 AM, "Lionel Crine" <[EMAIL PROTECTED]> wrote: > I have some trouble with javascript. > > > With a xhtml file like that
Javascript Error
I have some trouble with javascript. With a xhtml file like that : http://www.w3.org/1999/xhtml";> Open a Declaration --> notice the blank space the document is well displayed. BUT : whith this : http://www.w3.org/1999/xhtml";> Open a Declaration I have a b
RE: javascript in IE - was: [Re: javascript error]
CTED] > Envoyé : lundi 18 août 2003 16:24 > À : [EMAIL PROTECTED] > Objet : Re: javascript in IE - was: [Re: javascript error] > > > Yes your right, I met the same problem, and the same resolution... > > -- > Olivier > > > > On 18/08/2003 16:24, [EMAIL PROTECTED]
Re: javascript in IE - was: [Re: javascript error]
[EMAIL PROTECTED] wrote: i have notice that pages that include javascript code this way: served from cocoon (i think that cocoon has nothing to do with that) give blank results in IE. asking for "View source " you can see the generated xhtml code but IE display nothing changing to: every
Re: javascript in IE - was: [Re: javascript error]
Yes your right, I met the same problem, and the same resolution... -- Olivier On 18/08/2003 16:24, [EMAIL PROTECTED] wrote: i have notice that pages that include javascript code this way: served from cocoon (i think that cocoon has nothing to do with that) give blank results in IE. asking
Re: javascript error
It works now. Thanks guys. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
javascript in IE - was: [Re: javascript error]
i have notice that pages that include javascript code this way: served from cocoon (i think that cocoon has nothing to do with that) give blank results in IE. asking for "View source " you can see the generated xhtml code but IE display nothing changing to: everything work fine but its n
Re: javascript error
No no.. ;) http://www.w3.org/TR/xhtml1/#h-4.8 : scripts must be escaped by a CDATA section... but as Cedric wrote : an AND is "&&" in javascript... -- Olivier On 18/08/2003 16:14, frederic bertin wrote: Javascript in xhtml page should be handle in a particular way ? yes, this way: *
Fred
RE: javascript error
It's probably because an AND in javascript is && and not a single &. Hope that helps, Cedric -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED] Sent: 18 August 2003 15:04 To: [EMAIL PROTECTED] Subject: javascript error I wrote a little script :
RE: javascript error
Did you try the [CDATA[ ]] tags ? -Original Message- From: Lionel Crine [mailto:[EMAIL PROTECTED] Sent: maandag 18 augustus 2003 16:04 To: [EMAIL PROTECTED] Subject: javascript error I wrote a little script : function controle() { ... if (subgif != 'gif' &
javascript error
I wrote a little script : function controle() { ...
if (subgif != 'gif' & subgif != 'GIF') ... }
This xcript tests some illustration but the "&" entity create an error. I tried to write & instead but it doesn't work. Javascript in xhtml page
