Re: HELP!!!!! Double coercion exception in flowscript - SOLVED

2004-05-11 Thread Vadim Gritsenko
Tony Collen wrote:

Joerg Heinicke wrote:

On 10.05.2004 16:37, [EMAIL PROTECTED] wrote:

The problem was caused by a faulty syntax for the continuation id:

${continuation/id} should be #{$continuation/id}


http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107412183108550&w=4

Item 3.


Yeah, I'm not fond of the two possible syntaxes, and when I asked 
about it, I never got a clear answer beyond "so you can use either 
syntax" when I asked why there were two syntaxes to begin with. Huh?   
I'd like to deprecate one but where would you start?


Two syntaxes are for two different languages. One is jxpath, another is 
jexl. Start with choosing which one you want to remove, and which one to 
leave. What will be the criteria for choosing one over another?

Jxpath is already used in CForms, and I used jexl in situations where 
jxpath had bugs.

Vadim



RE: HELP!!!!! Double coercion exception in flowscript - SOLVED

2004-05-10 Thread H . vanderLinden
Yes, read the message in search of my problem, but it didn't hit home until
I actually found out it was the continuation id that I messed up. :-(

Bye, Helma

> -Original Message-
> From: Joerg Heinicke [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 10 May 2004 22:20
> To: [EMAIL PROTECTED]
> Subject: Re: HELP!!!!! Double coercion exception in 
> flowscript - SOLVED
> 
> 
> On 10.05.2004 16:37, [EMAIL PROTECTED] wrote:
> > The problem was caused by a faulty syntax for the continuation id:
> > 
> > ${continuation/id} should be #{$continuation/id}
> > 
> > Bye, Helma
> > 
> > 
> >>-Original Message-
> >>From: [EMAIL PROTECTED] 
> >>
> >>Hi,
> >>
> >>I run into a double coercion exception when I'm trying to 
> >>display a form using a flowscript.
> 
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107412183108550&w=4
> 
> Item 3.
> 
> ;-)
> 
> Joerg
> 


Re: HELP!!!!! Double coercion exception in flowscript - SOLVED

2004-05-10 Thread Tony Collen
Joerg Heinicke wrote:
On 10.05.2004 16:37, [EMAIL PROTECTED] wrote:

The problem was caused by a faulty syntax for the continuation id:

${continuation/id} should be #{$continuation/id}

Bye, Helma


-Original Message-
From: [EMAIL PROTECTED]
Hi,
I run into a double coercion exception when I'm trying to display a 
form using a flowscript.


http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107412183108550&w=4

Item 3.


Yeah, I'm not fond of the two possible syntaxes, and when I asked about it, I never got a clear 
answer beyond "so you can use either syntax" when I asked why there were two syntaxes to begin with. 
Huh?   I'd like to deprecate one but where would you start?

;-)

Joerg


Tony



Re: HELP!!!!! Double coercion exception in flowscript - SOLVED

2004-05-10 Thread Joerg Heinicke
On 10.05.2004 16:37, [EMAIL PROTECTED] wrote:
The problem was caused by a faulty syntax for the continuation id:

${continuation/id} should be #{$continuation/id}

Bye, Helma


-Original Message-
From: [EMAIL PROTECTED] 

Hi,

I run into a double coercion exception when I'm trying to 
display a form using a flowscript.
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107412183108550&w=4

Item 3.

;-)

Joerg


RE: HELP!!!!! Double coercion exception in flowscript - SOLVED

2004-05-10 Thread H . vanderLinden
The problem was caused by a faulty syntax for the continuation id:

${continuation/id} should be #{$continuation/id}

Bye, Helma

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 10 May 2004 14:05
> To: [EMAIL PROTECTED]
> Subject: HELP! Double coercion exception in flowscript
> 
> 
> Hi,
> 
> I run into a double coercion exception when I'm trying to 
> display a form using a flowscript. While debugging with the 
> flowscript editor I noticed that a second thread is started 
> and both threads run the flowscript function that is going to 
> display the form.
> 
> Can anyone tell me why this is happening and what I can do about it?
> 
> More specific: the webapp starts with a login form, when the 
> user logs in correctly a "search" page is shown. At this 
> point I have 1 thread as far as I can see. After submitting 
> the search request the result is displayed (1
> thread) and the user selects 1 record, which is then 
> displayed in detail
> (again: 1 thread as far as I can tell). Added to this page 
> are submenus and when I click on a menu item I get a second 
> thread with the above result.
> 
> 
> Note: I just (a few minutes ago) updated to the latest CVS 
> HEAD and the problem still exists.
> 
> 
> Bye,
> 
> Helma van der Linden
> Medical Informatics
> University Maastricht
> POBOX 616
> 6200 MD Maastricht
> The Netherlands
>