Hello, I'm having a problem deploying a Tapestry 4 web application in Tomcat 5/Websphere community edition. The war deploys fine on the contain, but when I attempt to access a page, I get the following:
Bean delegate has already been declared at (at Annotation @org.apache.tapestry.annotations.Bean(value=class java.lang.Object, initializer=, lifecycle=REQUEST) of public abstract org.apache.tapestry.valid.ValidationDelegate com.myapp.BaseMemberPage.getDelegate()) The bean is only declared at one place in the class (via annotations), so I'm unsure why both containers are complaining about the application trying to declare the bean again. Any ideas? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-4-Bean-already-defined-problem-tp5505256p5505256.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
