[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-761) Modify the default interception practices

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-761?page=all ]

Gavin King closed JBSEAM-761.
-----------------------------

    Resolution: Won't Fix

I've decided not to fix this because:

(a) you can work around by declaring toString() final
(b) I'm concerned about performance overhead of the Method.equals() that would be required
(c) there were no votes

If other people find this problematic, I'm prepared to reconsider.

> Modify the default interception practices
> -----------------------------------------
>
>                 Key: JBSEAM-761
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-761
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.1.0.GA
>         Environment: Any.
>            Reporter: Mike Quilleash
>         Assigned To: Gavin King
>             Fix For: 1.3.0.BETA1
>
>
> Currently all methods on a Seam component will be intercepted.  In some circumstances this can make debugging difficult as a lot of debuggers call toString() on objects visible from the breakpoint which executes all the Bijection incl the DisInjection which can damage the state of the object depending where the breakpoint is in the process.
> Perhaps the interception logic could ignore calls to any method on the Object class so the default toString() doesn't cause problems.
> Another complementary change would be to expand the @Intercept to be allowed on methods (and fields?) to allow the interception logic to be configured on individual methods (like a custom toString()) method.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira