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

Stefan Guggisberg updated SLING-1732:
-------------------------------------

    Description: 
it's currently impossible to debug scripted java servlets because of 
incompatible source file/java class names.

an example: 

an in-content java source file "/apps/foo/img.GET.java" declares the java class 
"apps.foo.img_GET".
the 'source file' debug attribute of the generated .class file has the value 
"img_GET.java" instead 
of "img.GET.java".

as a result, the source file is not found/displayed when a breakpoint is hit.  

  was:
it's currently impossible to debug scripted java servlets because of 
incompatible source file/java class names.

an example: 

an in-content java source file "/apps/foo/img.GET.java" declares the java class 
"apps.foo.img_GET".
the 'source file' debug attribute of the generated .class file has the value 
"img_GET.java" instead 
of "img.GET.java".

as a result, the source file is not found/displayed when a breakpoint s hit.  

    
> Scripted java servlets contain incorrect debug information
> ----------------------------------------------------------
>
>                 Key: SLING-1732
>                 URL: https://issues.apache.org/jira/browse/SLING-1732
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Java 1.0.0
>            Reporter: Stefan Guggisberg
>
> it's currently impossible to debug scripted java servlets because of 
> incompatible source file/java class names.
> an example: 
> an in-content java source file "/apps/foo/img.GET.java" declares the java 
> class "apps.foo.img_GET".
> the 'source file' debug attribute of the generated .class file has the value 
> "img_GET.java" instead 
> of "img.GET.java".
> as a result, the source file is not found/displayed when a breakpoint is hit. 
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to