Leo Sutic wrote:
>
>
>>From: Stephen McConnell [mailto:[EMAIL PROTECTED]]
>>
>>
>>>From: Nicola Ken
>>>And the Cocoon one is not entered by an assembler.
>>>It contains also params that change *per request*.
>>>
>>>
>>http://marc.theaimsgroup.com/?l=avalon-dev&m=102562981120502&w=2
>>
>>
>
>The solution does not handle the "per request" problem, as
>it requires the context to have a link to the container.
>
>
The criteria concerning context value creation should not be concerned
with the behaviour of the object it is creating. It is only concernined
with the instantiation of an object to add into the map. The example I
provdied in the above reference demonstrated one approach to creating
the Cocoon context object using the ContextFactory class. Things like
"per-request" behaviour is a concern of the implementation. Bottom line
is that if your running into restrictions concerning context instance
creation based on the expresivness of the ContextFactory model - chances
are that what you really should be doing is defining the object as a
component and leverage a more comprehensive construction approach.
Cheers, Steve.
>/LS
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
