Paul,
I would present it differently: with the annotation @RedirectionRef and the
more general @WebContext one, I can solve the following redirection use
cases:
- the redirection URI is dynamically produce with a POJO method
- the redirection can be expressed as a static URI template
- the redirection must be manually handled inside a processing method
I'm not proposing three ways of handling redirections, I'm proposing two
complimentary tools to solve all redirection use cases, including the one
illustrated above.
Best regards,
Jerome
> -----Message d'origine-----
> De : Paul.Sandoz_at_Sun.COM [mailto:Paul.Sandoz_at_Sun.COM]
> Envoyé : jeudi 12 avril 2007 23:11
> À : dev_at_jsr311.dev.java.net
> Objet : 3 solutions or 1 solution <was> Re: Redirection and
> creation <was> Re: Container Independence
>
> Hi Jerome,
>
> I will try once more to get my point across.
>
> You are proposing 3 different solutions to solve the redirect use-
> case. I am proposing 1 solution *.
>
> We need to have some really compelling use-cases to justify the
> increased complexity and triplication your solutions introduce.
>
> Paul.
>
> * debates about the number of classes vs. annotations and method
> signature constraints are just red herrings. Each can use a similar
> number of classes or annotations and each imposes constraints on the
> return type of the method signatures. There are minor
> differences and
> we don't need to quibble about them.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
>