Hello,
Anonymous has commented on
http://tapestry.apache.org/defining-tapestry-ioc-services.html.
You can find the comment here:
http://tapestry.apache.org/defining-tapestry-ioc-services.html#comment_2773
Please note that if the comment contains a hyperlink, it must be approved
before it is shown on the site.
Below is the reply that was posted:
~~~~
Thank you for your response, but I've already done that, and as I said
above, that approach only works for perthread scoped services. I'm looking for
an approach independent of any particular scope, something more general that be
applied via naming conventions and annotations just like most other aspects of
Tapestry. If this feature doesn't already exist, I hope it will be considered
in a future release of Tapestry.
~~~~
With regards,
The Apache Tapestry Project.
You are receiving this email because you have subscribed to changes for the
tapestry site.
To stop receiving these emails, unsubscribe from the mailing list that is
providing these notifications.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
