Are you using tapestry-spring?
No, I'm not using tapestry-spring. It turns out that I got it to work
correctly using only spring's ContextLoaderListener approach. And as you may
have guessed, it doesn't work when dropping tapestry-acegi into the
classpath. The exception I get is the same, An
No, I'm not using tapestry-spring.
Well, HiveMind needs to know how to find the Spring objects. So, just
drop tapestry-spring.jar into your WEB-INF/lib dir and see if that
fixes it (as long as your spring config file is named/located
appropriately).
What is the alternative way to
Hello James,
The tapestry-acegi library works...
I don't doubt it
...and it's been working flawlessly
I had it working that way too...until the problem, described erlier, cropped
up.
A qouple of questions:
Do you use JdbcDaoImpl or InMemoryDaoImpl?
Did you set up
Hello,
Following steps in this thread
http://forum.springframework.org/showthread.php?t=24013 I managed to get
acegi working using JdbcDaoImpl. Now I get an ApplicationRuntimeException as
soon as I call the webapp url. Unfortunatly, I can't rollback the changes
that affected this misbehavior,
The tapestry-acegi library works (we use it at work currently and it's
been working flawlessly). I don't know about the wiki page, but it
appears to be quite well written. I'm glad someone took the time to
document my work for me. :-)
On 12/14/06, Firas Adiler [EMAIL PROTECTED] wrote: