Re: T5.2 Coercion Confusion

2010-08-20 Thread Todd Orr
Head + palm. I must've changed that somewhere along the line. Thanks! On Fri, Aug 20, 2010 at 3:58 PM, Robert Zeigler wrote: > I've successfully converted a couple of T5.1 apps to T5.2 without > encountering anything like that.  And I have module (and use 3rd party > modules) that contribute to

Re: T5.2 Coercion Confusion

2010-08-20 Thread Robert Zeigler
I've successfully converted a couple of T5.1 apps to T5.2 without encountering anything like that. And I have module (and use 3rd party modules) that contribute to TypeCoercer with no issues, as well, so it definitely looks app-specific. One thing does come to mind, though. In your web.xml, wh

Re: T5.2 Coercion Confusion

2010-08-20 Thread Todd Orr
It appears that since upgrading from 5.1 to 5.2 Tapestry completely ignores my AppModule altogether. The only thing that has changed is the Tap version. Has anyone experienced this? On Fri, Aug 20, 2010 at 9:31 AM, Todd Orr wrote: > This used to work in 5.1.05: > >        public static void contr

T5.2 Coercion Confusion

2010-08-20 Thread Todd Orr
This used to work in 5.1.05: public static void contributeTypeCoercer(Configuration configuration) { configuration.add(new CoercionTuple(String.class, Class.class, new Coercion() { @Override public Class coerce(String input)