No. I think you can only do one way or the other at the moment.
Inge Solvoll wrote:
Does that configuration mean that you can't inject T5 IoC services into
spring?
On Tue, Mar 17, 2009 at 3:47 PM, Anthony Schexnaildre wrote:
Thank you.
-Anthony
On Mar 17, 2009, at 10:36 AM, Andy Pahne wro
Absolutrly not. I think it could actually be considered a bug that the old
context loader would actually allow that. Not only can I still load spring
services but it solved a threading issue with my webservices in the same
webapp (most likely due to tapestry trying to init it's own context).
-Anth
Does that configuration mean that you can't inject T5 IoC services into
spring?
On Tue, Mar 17, 2009 at 3:47 PM, Anthony Schexnaildre wrote:
> Thank you.
>
> -Anthony
>
>
> On Mar 17, 2009, at 10:36 AM, Andy Pahne wrote:
>
>
>> I think the reason is: the context is iniitialized twice. Once by the
Thank you.
-Anthony
On Mar 17, 2009, at 10:36 AM, Andy Pahne wrote:
I think the reason is: the context is iniitialized twice. Once by
the filter you defined in your web.xml and once by tapestry-spring.
If you prefer tapestry-spring NOT initializing your context, then
add this to your we
I think the reason is: the context is iniitialized twice. Once by the
filter you defined in your web.xml and once by tapestry-spring.
If you prefer tapestry-spring NOT initializing your context, then add
this to your web.xml
tapestry.use-external-spring-context
true
From my reading it seems Tap 5.1 is supposed to be backwards
compatible with 5.0.18 but not quite there yet. I am running Tapestry
in the same webapp as RestEasy. I am creating a root spring context
that both resteasy and tapestry share. I just added 5.1 to try it out
and I get an exception
