Hello!
snip/
I meant: if you want to achieve always the same result as by using
cocoon.getComponent() and you
need an access to WebApplicationContext directly then go with our own
version of WebAppContextUtils
that is aware of context switching. Anyway, using cocoon.getComponent() is
Patrick Heiden pisze:
Good Morning!
Hi Patrick.
I am still interested in understanding that appCtx-mechanisms. I've read
through several APIs and
several source files. After this first quick breed I could not find specific
class(es), wich is
responsible for load up block-specific contexts
Hi Patrick.
Hello Grzegorz!
I'm not surprised that you are confused becuase the whole issue is not
that easy to figure out, really.
Let me explain everything is managed.
First of all, root webAppCtx is initialized by Spring of course. Then it
reads the
applicationContext.xml[1] file
Patrick Heiden pisze:
snip/
You may now wonder what about sitemap-specific child containers. I don't want
to go into
details because I consider this functionality as legacy and not worth long
explanations.
However, if you really want to know the details I could share my knowledge.
I really
Good Morning!
I am still interested in understanding that appCtx-mechanisms. I've read
through several APIs and several source files. After this first quick breed I
could not find specific class(es), wich is responsible for load up
block-specific contexts and the whole webAppCtx respectively.
On 13.03.2008 06:21, Patrick Heiden wrote:
Could somebody please explain in wich order springs application context is
created (out of all 'block-specific' contexts inside
META-INF/cocoon/spring/*.xml).
I don't think the order of the block's spring.xml matter since AFAIK a
child context is
Joerg Heinicke wrote:
On 13.03.2008 06:21, Patrick Heiden wrote:
Could somebody please explain in wich order springs application
context is created (out of all 'block-specific' contexts inside
META-INF/cocoon/spring/*.xml).
I don't think the order of the block's spring.xml matter since
Could somebody please explain in wich order springs application
context is created (out of all 'block-specific' contexts inside
META-INF/cocoon/spring/*.xml).
I don't think the order of the block's spring.xml matter since AFAIK a
child context is created for every block extending a
Could somebody please explain in wich order springs application context is
created (out of all 'block-specific' contexts inside
META-INF/cocoon/spring/*.xml).
Thanks and greetings,
Patrick
--
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen:
