Now I know why I have to do this. I'm very much willing to type few
characters to make it easier for tapestry to do it's magic. Thank you :)
On Wed, Oct 31, 2012 at 11:05 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 31 Oct 2012 18:53:49 -0200, Muhammad Gelbana <m.gelb...@gmail.com>
> wrote:
>
> I can see the refactor-safe, auto complete and syntax check implied by
>> using marker annotations. I'm just wondering why should I specify unique
>> service IDs, because it's useless in that case. Don't you agree ?
>>
>
> Useless from the developer side, but very important for the Tapestry-IoC
> side. Having multiple services with a single id would be a mess. If you do
> an @InjectService("Id") and there are more than one service with that id,
> what should be injected? There's no good answer for that. ;) Yep, sometimes
> we have to do some stuff just to make the framework happy. In this case,
> it's just a matter of typing some characteres. :D
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
