Lewis Ship
>>
>> The new archetype doesn't have a dependency on tapestry-spring (it never
>>> did).
>>>
>
>
>
--
View this message in context:
http://www.nabble.com/-T5--5.1-Startup-probl
Solved. One shouldn't try to code that late and when tired. When copypasting
I used the tapestry-test definition in the pom and of course forgot to
delete the test for tapestry-spring sorry for the hassle.
2009/2/7 Otho
> I added that of course to them pom.xml along with other dependencies I
I added that of course to them pom.xml along with other dependencies I need.
The problem is, that my Spring context is read in correctly but then
Tapestry bails out with the classnotfoundexception for the
TaperstrySpringFilter.
2009/2/7 Howard Lewis Ship
> The new archetype doesn't have a depend
The new archetype doesn't have a dependency on tapestry-spring (it never did).
On Fri, Feb 6, 2009 at 2:19 PM, Otho wrote:
> After generating the new archetype I get a
>
> java.lang.ClassNotFoundException:
> org.apache.tapestry5.spring.TapestrySpringFilter
>
> The same error occurs also when usin
After generating the new archetype I get a
java.lang.ClassNotFoundException:
org.apache.tapestry5.spring.TapestrySpringFilter
The same error occurs also when using a ContextLoaderListener.
Tapestry-Spring and the TapestrySpringFilter are definitely in the
classpath. The spring beans are created n
