Vadim Gritsenko wrote:
Daniel Fagerstrom wrote:
oceatoon wrote:
Why step away from the global session though,
and create a new FOM_session structure? your answer was "design
decision
but I don't understand, why ?
Neither do I, it wasn't my decison but Chris Olivers. One reason
might be that flow
Daniel Fagerstrom wrote:
oceatoon wrote:
Why step away from the global session
though,
and create a new FOM_session structure? your answer was "design decision
but I don't understand, why ?
Neither do I, it wasn't my decison but Chris Olivers. One reason might
be that flow uses a special embedin
oceatoon wrote:
Daniel Fagerstrom wrote:
I agree with that the behaviour is weird, but it is designed to be that
way. What happens is that your data is always placed in the session data
in the servlet. But then the request object, session objects etc are
placed in a different place if you use them
Daniel Fagerstrom wrote:
> I agree with that the behaviour is weird, but it is designed to be that
> way. What happens is that your data is always placed in the session data
> in the servlet. But then the request object, session objects etc are
> placed in a different place if you use them from
oceatoon wrote:
Daniel Fagerstrom wrote:
In the refactored JXTG I use o.a.c.environment.FlowObjectModelHelper,
that Carsten wrote. It gets the objects from the normal places in the
objectmodel and does the dynamic map embeding and puts everything in
$cocoon. By using this we get the same behaviour
Daniel Fagerstrom wrote:
> I agree with that the behaviour is weird, but it is designed to be that
> way. What happens is that your data is always placed in the session data
> in the servlet. But then the request object, session objects etc are
> placed in a different place if you use them from
I agree with that the behaviour is weird, but it is designed to be that
way. What happens is that your data is always placed in the session data
in the servlet. But then the request object, session objects etc are
placed in a different place if you use them from flow, comperd with how
it is do
HI everyone
We are having weird effects poping up some structure questions about FOM and
more precisly about FOM_session. I use Flow to put some data into
cocoon.session.setAttribute("data",data) and retreive this easily from my
jx file coming from flow.
Thinking this is part of a global session
