Re: JSR311: Targets for _at_*Param, _at_DefaultValue, _at_Encoded

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Thu, 20 Mar 2008 16:32:51 +0100

Stephan Koops wrote:
> Do you (and all) agree, that the specification should primarily
> support the default lifecycle (instantiation per request), but make
> other lifecycles possible?

I do.

> *clarify missunderstanding* (solution proposal later)
>> The use of: String s = tlCharSequence.get().toString();
>> is really convoluted and ugly.
> I think here is a misunderstanding. My proposals mean:
> @*Param(...) private CharSequence charSequence;
> Default lifecycle runtime environments inject a String, singelton
> runtimes inject a proxy CharSequence, which will return the String by
> toString(). It is read by
> charSequence.toString();
> and returns the String for the current Thread. Works for both
> lifecycles.

Yes but would the average developer know that CharSequence et. al. need
not be ThreadLocal wrapped but String et. al. should be?

> BTW: tomorrow (Good Friday) and on monday it's public holiday in
> Germany and I will not look into my mailbox.

Hope you have a nice break, i will be off Monday as well: Le vendredi
est moins bonne en France comme en Allemagne (apologies if this is like
fingers scraping on blackboards for the native French on the list!).


| ? + ? = To question
    Paul Sandoz