Eager loading services is incompatible with live service reloading.
-------------------------------------------------------------------
Key: TAP5-1076
URL: https://issues.apache.org/jira/browse/TAP5-1076
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-ioc
Affects Versions: 5.2.0
Reporter: Christophe Cordenier
Howard's comment on user mailling list:
Basically, when using reloadable, the object at the end of the
delegate/advice stack, which is normally the service implementation,
is itself a proxy that performs live class reloading. Currently, it
does not attempt to load the service implementation until needed, but
that can and should be changed, giving reloaded services that same
semantics as non-reloadable services (just with one extra level of
proxy).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
