You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/03/25 20:37:27 UTC

[jira] Closed: (TAP5-1079) Live class reloading should extend to proxied objects (such as from ObjectLocator.proxy()

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

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

       Resolution: Fixed
    Fix Version/s: 5.2.0

... and, when appropriate, Configuration.addInstance() and etc.  If Tapestry was autobuilding it before, it may now proxy it (with reloading) when there's a local class file

> Live class reloading should extend to proxied objects (such as from ObjectLocator.proxy()
> -----------------------------------------------------------------------------------------
>
>                 Key: TAP5-1079
>                 URL: https://issues.apache.org/jira/browse/TAP5-1079
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-ioc
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.0
>
>
> In other words, if it is proxiable (because there's an interface and an implementation class for that interface) then make with the live class reloading.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.