From: Stephan Coboos [mailto:[EMAIL PROTECTED]
> From: "Antonio Gallardo"
>
> > Hi:
> >
> > You need to call releaseComponent() before sendPage() or
> > sendPageAndWait()
> >
> > Antonio Gallardo
>
> Thank you Antonio and Reinhard but I think, this is very very
> uncomfortable, isn't it? At the same way we had to deal (at
> the past ;-)) with objects in the different scopes in servlet
> programming: "Before sending a response we have to save our
> objects into the session scope". In flowscript there is the
> opposite case: "Before sending a page release the object".
> Therefore I can't deal the whole script long with the same
> component. After each call of sendPage... I have to retrieve
> a new one. Very very uncomfortable... ;-))
yep we know and this has been discussed several times. one possible
approach could be intercepted flowscript functions:
function myFunc() {
var myComp = cocoon.getComponent( "myComponent" );
cocoon.sendPageAndWait( "firstPage", {} );
cocoon.sendPageAndWait( "firstPage", {} );
cocoon.sendPageAndWait( "firstPage", {} );
}
Intercpeption:
function myFunc() {
stopExectution(): {
cocoon.releaseComponent( myComp );
}
continueExecution(): {
myComp = cocoon.getComponent( "myComponent" );
}
}
Checkout the scratchpad block of 2.1 to find more.
I'll investigate further on this in the next weeks and also move it to
Cocoon 2.2.
Additionally there has also been a prototyp by Christopher that does all
the magic without user defined interceptions but has never reached CVS
(checkout the archives to find out more).
Cheers,
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
