Damir Bijuklic wrote:
Hi,
I have actually found a solution in Spring docs. You need to put spring
RequestContextFilter before t5 filter, like this:
[...]
It would be great if you could add an HowTo for this discover, to let
the other knows about that - I'm quite sur some other will thank
needed.
From: Howard Lewis Ship
To: Tapestry users
Sent: Wednesday, 4 February, 2009 22:44:30
Subject: Re: T5 - spring integration
Scope 'session' is not active for the current thread
looks like a Spring exception; seems like its wanting some per-th
Scope 'session' is not active for the current thread
looks like a Spring exception; seems like its wanting some per-thread
setup. That's easy enough to do, I just haven't used Spring @Scope
before and I didn't know about it. If you could add a JIRA Issue, with
pointers to the appropriate Spring d
I'm just taking a guess here, but I think it won't. As far as I know
the tapestry spring integration was always limited to singleton beans.
I think the "prototype" variant is maybe difficult to handle since
tapestry ioc (and hivemind in the past) have a somewhat different
approach on object creatio
As I mentioned, my Spring configurations is confirmed as working. I was
using 5.0.3 which I assumed was the latest as it's the one mentioned on the
first page as the most recent SNAPSHOT. What's the best way to keep track of
the latest available SNAPSHOT?
A big "Thanks" to everyone who took the t
Hi,
There is a new syntax with 5.0.4-SNAPSHOT and the URL
http://tapestry.apache.org/tapestry5/tapestry-spring/ was updated a while
ago. There is no more @Inject("spring:yourBean").
It works fine for me.
Here is an excerpt:
public class UserView {
@Inject
@SpringBean("userManager")
pr
If you develop base on Tapestry 5.0.3
Please use
@Inject("Spring:groupRepository")
Instead of
@Inject
@SpringBean("groupRepository")
'groupRepository' is just your the bean id defined in your spring's
configuration file.
This is my first to answer question in mail list
2007/4/24, Mat
On 4/24/07, Matt Welch <[EMAIL PROTECTED]> wrote:
I'm sure I must be doing something wrong, but for lthe life of me, I can't
figure out what it is.
I'm not trying anything complicated. I've confirmed that my Spring beans are
accessible in my webapp so I know the Spring part of my configuration
If you develop base on Tapestry 5.0.3
Please use
@Inject("Spring:groupRepository")
Instead of
@Inject
@SpringBean("groupRepository")
'groupRepository' is just your the bean id defined in your spring's
configuration file.
This is my first to answer question in mail list . I have never
Hmm, I'm not sure which way the docs are out of sync - future or past.
http://tapestry.apache.org/tapestry5/tapestry-spring/
You'll see further down the page after the example it mentions "Spring:UserDAO".
That's what I'm using with 5.0.3 SNAPSHOT and it works. Try
@Inject("spring:groupRepos
On 2/19/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Yep, and all of this stuff will be rolled into a tapestry-spring Maven
archetype.
The tapestry-spring-integration module will support
@Inject("spring:bean") to allow access to anything in the Spring bean
context.
I've already done the s
Yep, and all of this stuff will be rolled into a tapestry-spring Maven
archetype.
The tapestry-spring-integration module will support
@Inject("spring:bean") to allow access to anything in the Spring bean
context.
On 2/19/07, D&J Gredler <[EMAIL PROTECTED]> wrote:
Good catch :-)
You also have t
I think what is needed, though, is something that allows you to bind
spring beans directly into your page/components. Having to lookup
spring beans all the time can be a pain.
On 2/19/07, D&J Gredler <[EMAIL PROTECTED]> wrote:
Good catch :-)
You also have to add the following line to your web
Good catch :-)
You also have to add the following line to your web.xml:
org.springframework.web.context.ContextLoaderListener
On 2/19/07, James Carman <[EMAIL PROTECTED]> wrote:
Of course, you have to set up the ContextLoaderListener, right?
On 2/19/07, D&J Gredler <[EMAIL PROTECTED]> wr
Of course, you have to set up the ContextLoaderListener, right?
On 2/19/07, D&J Gredler <[EMAIL PROTECTED]> wrote:
You can just inject the following into your pages:
@Inject
private ApplicationGlobals globals;
And then use the servlet context inside the globals object to get the
appli
You can just inject the following into your pages:
@Inject
private ApplicationGlobals globals;
And then use the servlet context inside the globals object to get the
application context via
WebApplicationContextUtils.getRequiredWebApplicationContext
(servletContext);
Once you have the
16 matches
Mail list logo
