dev@jsr311.java.net

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

From: John Harby <jharby_at_gmail.com>
Date: Wed, 12 Mar 2008 14:25:09 -0700

I agree with (v) on the flexibility argument.

On Wed, Mar 12, 2008 at 1:22 AM, Heiko Braun <hbraun_at_redhat.com> wrote:
>
> After reconsidering the recent arguments,
> I'll have to admit that the particular use cases haven't been all clear
> to me. I'll revisit my vote and go for (v).
>
> /Heiko
>
>
>
>
> On Tue, 2008-03-11 at 18:45 +0100, Heiko Braun wrote:
> >
> > I am voting for (i), the status quo.
> >
> > /Heiko
> >
> > On Tue, 2008-03-11 at 13:36 -0400, Marc Hadley wrote:
> > > There's been a lot of discussion of whether or not to expand the
> > > targets (i.e. what Java artifacts you can use the annotation on) of
> > > the @*Param annotations (i.e. @PathParam etc al). If we do add targets
> > > for these annotations I think we also need to do the same for
> > > @DefaultValue and @Encoded. I'm uncomfortable adding targets that are
> > > only supported in some implementations so if we do add targets they
> > > will be required to be supported on resource classes (not providers)
> > > in all implementations.
> > >
> > > Discussion so far has been between Bill, Stephan and myself, I'd like
> > > to hear from others hence this poll. Please choose from the following
> > > and reply to the list with your selection. Silence means you don't
> > > care what happens - how could that be ;-).
> > >
> > > Here are the options for target I see:
> > >
> > > (i) Parameter. The status quo. Works with any lifecycle.
> > > (ii) Parameter and field. Spec will warn that use on a field in a
> > > singleton resource isn't supported.
> > > (iii) Parameter and field. Spec will require use of a proxy for field
> > > injection. Pro: singletons can be supported. Con: will affect
> > > performance. Con: still won't work for simple types, spec will warn
> > > about this.
> > > (iv) Parameter, field and method (bean setter). Spec will warn that
> > > use on a field in a singleton resource isn't supported and that use on
> > > method will require application-managed thread-local handling. Pro:
> > > bean setter enable support for singletons. Con: complicated bean
> > > setters.
> > > (v) Parameter, field and method (bean setter). Spec will require use
> > > of a proxy for field and method injection. Same pros and cons as (iii).
> > >
> > > Vote early, vote once.
> > > Marc.
> > >
> > > ---
> > > Marc Hadley <marc.hadley at sun.com>
> > > CTO Office, Sun Microsystems.
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> > > For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> > For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>
>