I was the original one to open up the JIRA issue about annotations and the binding issues. I still occasionally get the exception but its very difficult to reproduce. I've also switched to jetty for development and it has seemed to help with it.
On 7/24/06, Nick Faiz <[EMAIL PROTECTED]> wrote:
Jesse, Thanks, but it's really a hard one to reproduce. It seems to follow in the wake of db failures. If I can reliably reproduce it I will follow the steps you suggest. Nick Jesse Kuhnert wrote: > No idea what the problem is, but if you give a more complete example > (preferrably attached to something in JIRA), I'm sure I can knock out a > solution in relatively short time. (time being directly proportional > to how > easy it is to re-produce your problem in a test case) > > On 7/24/06, Nick Faiz <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> Has anyone else encountered this error? >> >> Bean delegate has already been declared (at Annotation >> @org.apache.tapestry.annotations.Bean(value=class java.lang.Object, >> lifecycle=REQUEST, initializer=) of public abstract >> org.apache.tapestry.valid.ValidationDelegate >> com.voiplogic.portal.components.PortalComponent.getDelegate()). >> >> At least one other developer has - >> >> http://mail-archives.apache.org/mod_mbox/jakarta-tapestry-dev/200602.mbox/[EMAIL PROTECTED] >> >> >> I think it is a show stopper. In our case it is slowing down development >> work dramatically. >> >> Any ideas or clues would be appreciated. >> >> >> Cheers, >> Nick Faiz >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- ~chris
