cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ricardo Rocha <rica...@apache.org>
Subject Re: More on FOM
Date Mon, 30 Jun 2003 15:48:22 GMT
Reinhard Pötz wrote:

>>- There should be unrestricted access to all components via
>>cocoon.getComponent(id). 
> 
> I'll implement getComponent( id ) and releaseComponent( component) ASAP
> because the current flow implementation exposes the component manager
> and this leads to a serious bug! If you have more than one user the
> component manager can become null. This can be very annoying if you want
> to train some people ...

Cool :-)

>>Among other goodies, this will give indirect access to Actions and Modules
 >> without providing explicit FOM support for them. Access to request
 >> input modules, in particular, should account for request.getURI().
> 
> AFAIK many of them need the object model and this is not provided by the
> flow so I think you have no chance to use the actions and input modules
> which need objects of the object model. Am I right here?

Yes, you are... :-(

>>- Access to continuation objects should be provided.
>>	var kont = sendPageAndWait(uri, data)
>>This is deemed necessary as certain continuation usage
>>patterns may call 
>>for explicit, programmatic invalidation of continuations.
>>	- Properties
>>		- id
>>	- Methods
>>		- getParent()
>>		- getChildren()
>>		- invalidate()
>>	- Events
>>		- onExpiration()
>>
> 
> sounds good. It should also be possible to create your own continuations
> objects without sending a page. See the JXForms implementation which
> needs this to provide previous/next-navigation.

Yes, creating continuations without sending pages is all-important.

> I'll add all those things to the proposal ASAP.

Hey Reinhard, you're a committed committer, cool!

Regards,

Ricardo



Mime
View raw message