You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/06/14 23:13:13 UTC

[jira] Created: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
----------------------------------------------------------------------------------------------------------------------

                 Key: TAP5-1188
                 URL: https://issues.apache.org/jira/browse/TAP5-1188
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
    Affects Versions: 5.2.0
            Reporter: Howard M. Lewis Ship


As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Closed: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.

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

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

    Fix Version/s: 5.2.1
       Resolution: Fixed

Did a bunch of work to extend the "class loading umbrella" for a reloadable service to other classes in the same package, but also the base class

> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.1
>
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Assigned: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.

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

Howard M. Lewis Ship reassigned TAP5-1188:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Commented: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Hudson (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/TAP5-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904855#action_12904855 ] 

Hudson commented on TAP5-1188:
------------------------------

Integrated in tapestry-5.2-freestyle #185 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/185/])
    TAP5-1188: Remove commented-out code
TAP5-1188: Clean up and streamline code, make sure all inner classes (including inner interfaces) are loaded by the reloading class loader
TAP5-1188: Add test to demonstrate that changing a base class reloads the service
TAP5-1188: Make use of URLChangeTracker to track which file(s) may have changed, forcing a service to reload
TAP5-1188: Refactory URLChangeTracker from tapestry-core to tapestry-ioc
TAP5-1188: Tune some of the logic related to which classes are reloaded
TAP5-1188: Refactor to use Javassist class loading objects


> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.1
>
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Closed: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.

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

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

    Fix Version/s: 5.2.1
       Resolution: Fixed

Did a bunch of work to extend the "class loading umbrella" for a reloadable service to other classes in the same package, but also the base class

> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.1
>
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Commented: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Hudson (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/jira/browse/TAP5-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904855#action_12904855 ] 

Hudson commented on TAP5-1188:
------------------------------

Integrated in tapestry-5.2-freestyle #185 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/185/])
    TAP5-1188: Remove commented-out code
TAP5-1188: Clean up and streamline code, make sure all inner classes (including inner interfaces) are loaded by the reloading class loader
TAP5-1188: Add test to demonstrate that changing a base class reloads the service
TAP5-1188: Make use of URLChangeTracker to track which file(s) may have changed, forcing a service to reload
TAP5-1188: Refactory URLChangeTracker from tapestry-core to tapestry-ioc
TAP5-1188: Tune some of the logic related to which classes are reloaded
TAP5-1188: Refactor to use Javassist class loading objects


> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.2.1
>
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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

[jira] Assigned: (TAP5-1188) Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions

Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.

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

Howard M. Lewis Ship reassigned TAP5-1188:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> Refactoring the base class of a live-reloaded service implementation can cause mysterious NoSuchMethodError exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1188
>                 URL: https://issues.apache.org/jira/browse/TAP5-1188
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.0
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> As currently implemented, live class reloading only takes into account the service implementation class (plus any inner classes of the implemention class). If the implementation class extends from a base class, the base class is not scanned for changes, and is not reloaded when it (or the actual implementation class) changes.

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