Simone Gianni wrote:
> Hi Carsten,
> maybe I'm missing something, but isn't there a ProcessInfoProvider, with
> which you can access request, response, servlet context and object model
> (and from there all the rest)?
>
Yes, this is one part of the story. If you're able to get the
ProcessInfoProvi
Hi Carsten,
maybe I'm missing something, but isn't there a ProcessInfoProvider, with
which you can access request, response, servlet context and object model
(and from there all the rest)?
It ends in a thread local anyway, since uses the environment stack
Daniel told about.
If this is not the rig
Daniel Fagerstrom wrote:
>
> I think that a sitemap scope could solve a large part of our needs.
>
Hmm, yes, together with the RequestContextHolder from Spring it should
solve most of our problems. The RequestContextHolder makes only the
attributes of a request available. Fortunately we already s
Carsten Ziegeler skrev:
Daniel Fagerstrom wrote:
Can you give some specific examples where you need this?
We often have the problem to get the current service manager. The whole
code base contains various calls to the EnvironmentHelper class to get
this service manager.
For those in the audie
Hi Daniel, Carsten,
Carsten Ziegeler skrev:
During development you sometimes face the problem that you need
access
to specific information, like the current request object (or its
parameters), the Spring application context, the servlet context etc.
In an ideal world where everything is a c
Daniel Fagerstrom wrote:
> Can you give some specific examples where you need this?
We often have the problem to get the current service manager. The whole
code base contains various calls to the EnvironmentHelper class to get
this service manager. One main reason for this are utility methods like
Carsten Ziegeler skrev:
During development you sometimes face the problem that you need access
to specific information, like the current request object (or its
parameters), the Spring application context, the servlet context etc.
In an ideal world where everything is a component, this is no issu
During development you sometimes face the problem that you need access
to specific information, like the current request object (or its
parameters), the Spring application context, the servlet context etc.
In an ideal world where everything is a component, this is no issue as
the container provide
