The outcome should be failure, but it should be reported more
reasonably, and not hit an StackOverflow. Were either of these proper
services (with an interface) the proxy would have identified the
circular dependency.
On Mon, Sep 1, 2008 at 12:35 AM, Kristian Marinkovic
<[EMAIL PROTECTED]> wrote:
Might be good to do an on-registration circular dependency check to
ensure that services cannot be defined if they would cause a cycle.
I'd open a JIRA but I'm lazy. (Ok, I'll open one tomorrow. I'm
going to sleep now)
Christian.
On 1-Sep-08, at 03:35 , Kristian Marinkovic wrote:
U
Unlike Hivemind, T5 IOC creates proxies only for interfaces... this is
intended behaviour
Michel Jeanson <[EMAIL PROTECTED]>
Gesendet von: news <[EMAIL PROTECTED]>
01.09.2008 00:07
Bitte antworten an
"Tapestry users"
An
users@tapestry.apache.org
Kopie
Thema
Circular dependencies in Tap5
