On Fri, 16 Jul 2010 22:35:03 -0300, Christian Gruber
wrote:
(that last message came out a little cattier than I meant, Thiago.
Sorry)
No problem, Christian. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owne
(that last message came out a little cattier than I meant, Thiago. Sorry)
On Fri, Jul 16, 2010 at 7:36 PM, Christian Edward Gruber <
christianedwardgru...@gmail.com> wrote:
> Heh. I don't need to be schooled in "web development" :) But most ioc
> frameworks have a web-centric naming for such a
Heh. I don't need to be schooled in "web development" :) But most
ioc frameworks have a web-centric naming for such a scope, and I
wanted to be sure that the right way to do it was with per-thread.
cheers,
Christian.
On Jul 16, 2010, at 3:24 PM, Thiago H. de Paula Figueiredo wrote:
On Fri
On Fri, 16 Jul 2010 16:07:58 -0300, Christian Edward Gruber
wrote:
I need to bind a service into request scope, so it's whatever I need to
do in my module.
In web applications, unless you create new threads, request scope is the
same as thread scope. If this is not your scenario, creatin
I need to bind a service into request scope, so it's whatever I need
to do in my module.
On Jul 16, 2010, at 3:03 PM, Thiago H. de Paula Figueiredo wrote:
On Fri, 16 Jul 2010 15:30:15 -0300, Christian Edward Gruber > wrote:
I see singleton and per-thread... and there's an implicit session
On Fri, 16 Jul 2010 15:30:15 -0300, Christian Edward Gruber
wrote:
I see singleton and per-thread... and there's an implicit session scope
wiht SessionState annotations...
Are there "session" and "reqeust" scopes?
As a T-IoC scope, no. There are annotations and services that use the
se
Check. Ok - I wasn't sure about per-thread, since it's possible to
implement thread scope against a request object, instead of per-thread.
thanks,
Christian.
On Jul 16, 2010, at 2:39 PM, Howard Lewis Ship wrote:
per-thread is the same as request within a Tapestry application.
There's been t
per-thread is the same as request within a Tapestry application.
There's been talk about a sesson scope, but it doesn't exist.
SessionState are not services so there's no scope for them.
On Fri, Jul 16, 2010 at 11:30 AM, Christian Edward Gruber
wrote:
> I see singleton and per-thread... and there
I see singleton and per-thread... and there's an implicit session
scope wiht SessionState annotations...
Are there "session" and "reqeust" scopes? I've managed to avoid a
request-scoped object until now, but I think I need one in the ioc...
but I don't see these two scopes explicitly docu
