One of the things you might want to look at in your tests is: http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ioc/services/TypeCoercer.html#explain(java.lang.Class, java.lang.Class)
Given an input type and an output type, this returns a string that shows how the TypeCoercer will do the transform. It is often very useful in unit tests of code that provides coercions, especially if you are contributing a bunch of coercions and aren't sure how they will interact. On Mon, Nov 12, 2012 at 3:20 PM, bhorvat <horvat.z.bo...@gmail.com> wrote: > Cool. I learned a bit today I guess > > tnx for help > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Type-Coercer-for-Joda-Time-tp5717942p5717960.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com
