Chances are good this is related to a client-side persistent property, or a property stored inside a form using Hidden.
A type converter is most likely being used to convert from a string to some server-side type. Perhaps you tried to update a property that is really an entity type? A stack trace would help narrow it down. On 12/12/06, Ed Cohen <[EMAIL PROTECTED]> wrote:
When refreshing a form, I get the error: "No type converter for type TypeABC" My question is: Why does Tapestry (4.0) invoke a "type converter". What does Tapestry use it for? Ed
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com