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 2011/02/11 11:02:57 UTC
[jira] Assigned: (TAP5-1208) Debugging in Tapestry 5.2
[ https://issues.apache.org/jira/browse/TAP5-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1208:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Debugging in Tapestry 5.2
> -------------------------
>
> Key: TAP5-1208
> URL: https://issues.apache.org/jira/browse/TAP5-1208
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-ioc
> Affects Versions: 5.2.0, 5.2
> Reporter: Mike M Pestorich
> Assignee: Howard M. Lewis Ship
> Priority: Minor
>
> Improvement related to May 2010 thread: [T5] debugging in eclipse
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201005.mbox/%3CAANLkTinOfXeSmALOYxzR-OSd4uZwTDC_Qt1j4igZgVFP@mail.gmail.com%3E
> As noted in the thread, values can only be seen when debugging by inspecting the related conduit due to the class transformation that takes place behind the scenes.
> Actually, in my experience, this used to be the case but now with the most recent snapshots I can't even do that.
> Later on in the thread a suggestion is made to modify UncaimedFieldWorker.
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201005.mbox/%3CAANLkTimTAtLKsZbYntUm2pwN70KiwnnwlwJr4gmWL9V3@mail.gmail.com%3E
> I don't know if this is correct or not but I would think that this would be a useful improvement over the way things currently work.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira