tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-1076) When a service implementation is reloadable, it will not eager load
Date Thu, 25 Mar 2010 19:51:31 GMT

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

Howard M. Lewis Ship closed TAP5-1076.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.0

> 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.


Mime
View raw message