dont get me wrong, technically it is OK, it is just the logic is unclear and code redundant.
In my opinion frameworks are build to simplify work, that's why I said it should ring bells - this goes in wrong direction. I perfectly understand that Component has no idea of type declared on descendant but for me it simply doesnt matter. Component should knew itself that it has converter and if there is none it should ask application for any. now this two step process is implemented in one method. I just dont understand why getting converter is so strict right now, thats all pozdrawiam Paweł Kamiński [email protected] [email protected] ______________________ On 27 November 2011 15:55, Martin Grigorov <[email protected]> wrote: > Hi, > > On Sun, Nov 27, 2011 at 3:52 PM, kamiseq <[email protected]> wrote: >> well yeah this is exactly the same except for locator. >> >> code like this >> public final <C> IConverter<C> getConverter(Class<C> clazz) >> { >> if (Date.class.isAssignableFrom(clazz)) >> { >> return (IConverter<C>)converter; >> } >> else >> { >> return super.getConverter(clazz); >> } >> } >> should always ring bells that something is wrong. > > Care to explain what exactly is wrong ? > >> >> anyway I think that type checking should be done while registering the >> converter and not while getting it. >> >> pozdrawiam >> Paweł Kamiński >> >> [email protected] >> [email protected] >> ______________________ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com > > --------------------------------------------------------------------- > 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]
