Hi Sebastian, > Qualified classnames for the conversion makes it harder to use. > > Given that there aren't many different types, I'm intending to use a > simple naming convention that is documented in an example parameters > file.
I was thinking ahead for the future. We don't know what kind of parameters may be required in the future. Arrays of MessageFormat to parse dates in cookies, for example? > It is easy enough for the user to look at the parameter page and work > out the corresponding property name. Sure. I still recommend $int rather than $Integer :-) > But if you are considering adding something to HttpClient, then > perhaps it would be worth considering some form of parameter name + > type registry, perhaps via annotations. This information could be used > to validate parameters, and the list could be compared against the > user documentation. Or maybe the documentation could be generated from > the annotations? I doubt we'll have spare time for that before 2008. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
