[jira] Updated: (TAP5-1076) When a service implementation is reloadable, it will not eager load

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship updated TAP5-1076:
---------------------------------------

    Summary: When a service implementation is reloadable, it will not eager load  (was: Eager loading services is incompatible with live service reloading.)

... because instantiating the service eagerly only instantiates another layer of just-in-time object creation (the proxy around the live-reloaded implementation).  Fortunately, it's easy to force the innermost proxy to create an object if eager loading.

> When a service implementation is reloadable, it will not eager load
> -------------------------------------------------------------------
>
>                 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
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> 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.