I was referring to the exception being rare, not third party implementations.
Keep in mind that the exception will only occur when invoking the new method on ComponentResources. At the moment there is no such code in existence. On 20 May 2014 13:51, "Thiago H de Paula Figueiredo" <thiag...@gmail.com> wrote: > On Tue, 20 May 2014 07:20:21 -0300, Lance Java <lance.j...@googlemail.com> > wrote: > > This would only occur in third party bindings / propertyConduits that >> don't extend core (internal) implementations. >> >> IMHO these exceptions are likely to be rare as hen's teeth ;) >> > > Agreed for ComponentResources, less agreed for Binding and disagreed for > PropertyConduit, which is used inside some projects to implement some > properties for BeanModel-based components. This is *not* uncommon to be > found in non-library code. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >
