You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ognen Ivanovski (JIRA)" <de...@tapestry.apache.org> on 2007/10/25 17:40:50 UTC
[jira] Created: (TAPESTRY-1859) Improve debugging "experience" in
IDE (java assist)
Improve debugging "experience" in IDE (java assist)
---------------------------------------------------
Key: TAPESTRY-1859
URL: https://issues.apache.org/jira/browse/TAPESTRY-1859
Project: Tapestry
Issue Type: Improvement
Affects Versions: 5.0.6
Reporter: Ognen Ivanovski
Priority: Minor
If possible, improve step-into debug info in proxies and bindings. Typical usage scenarios are:
- trying to step into a binding (the debugger should jump directly into the getter method)
- trying to step into a call to an injected service or component
- trying to step into a call to a service through a tapestry-ioc proxy
In the last two cases the debugger would
- directly go to the service method implementation
- if the service is not already created it would jump to the service creation method (or constructor if bind() is used)
- upon return from the creation method / constructor it would directly go to the service call
The general idea is not to allow the developer to step into java assist code.
This would greatly improve the ease-of-development as well as the learnability of tapestry (as newbies often resort to the debugger to see "what's going on inside").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAP5-118) Improve debugging "experience" in IDE
(java assist)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-118:
--------------------------------------
Issue Type: New Feature (was: Bug)
> Improve debugging "experience" in IDE (java assist)
> ---------------------------------------------------
>
> Key: TAP5-118
> URL: https://issues.apache.org/jira/browse/TAP5-118
> Project: Tapestry 5
> Issue Type: New Feature
> Affects Versions: 5.0.15
> Reporter: Ognen Ivanovski
> Priority: Minor
>
> If possible, improve step-into debug info in proxies and bindings. Typical usage scenarios are:
> - trying to step into a binding (the debugger should jump directly into the getter method)
> - trying to step into a call to an injected service or component
> - trying to step into a call to a service through a tapestry-ioc proxy
> In the last two cases the debugger would
> - directly go to the service method implementation
> - if the service is not already created it would jump to the service creation method (or constructor if bind() is used)
> - upon return from the creation method / constructor it would directly go to the service call
> The general idea is not to allow the developer to step into java assist code.
> This would greatly improve the ease-of-development as well as the learnability of tapestry (as newbies often resort to the debugger to see "what's going on inside").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Updated: (TAPESTRY-1859) Improve debugging "experience" in
IDE (java assist)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1859:
-------------------------------------------
Fix Version/s: 5.1
> Improve debugging "experience" in IDE (java assist)
> ---------------------------------------------------
>
> Key: TAPESTRY-1859
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1859
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.6
> Reporter: Ognen Ivanovski
> Priority: Minor
> Fix For: 5.1
>
>
> If possible, improve step-into debug info in proxies and bindings. Typical usage scenarios are:
> - trying to step into a binding (the debugger should jump directly into the getter method)
> - trying to step into a call to an injected service or component
> - trying to step into a call to a service through a tapestry-ioc proxy
> In the last two cases the debugger would
> - directly go to the service method implementation
> - if the service is not already created it would jump to the service creation method (or constructor if bind() is used)
> - upon return from the creation method / constructor it would directly go to the service call
> The general idea is not to allow the developer to step into java assist code.
> This would greatly improve the ease-of-development as well as the learnability of tapestry (as newbies often resort to the debugger to see "what's going on inside").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org