[
https://issues.apache.org/jira/browse/SLING-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580521#comment-14580521
]
Dan Klco commented on SLING-4792:
---------------------------------
This is a convenience tool for developers. When you encounter a Runtime
Exception in a JSP, the stack trace will point back to the line number in the
Java file created for that JSP. When the ClassLoader was repository-based, you
could navigate to /var/classes to find the corresponding Java file. With the
FSClassLoader putting the files in the Bundle data directory this is more
cumbersome.
> FS ClassLoader Find .java File
> ------------------------------
>
> Key: SLING-4792
> URL: https://issues.apache.org/jira/browse/SLING-4792
> Project: Sling
> Issue Type: Improvement
> Affects Versions: File System ClassLoader 1.0.0
> Reporter: Dan Klco
> Labels: features
> Fix For: File System ClassLoader 1.0.2
>
>
> With SLING-4707, finding the .java files associated with a compiled script
> has been made more difficult as you need to find the ID of the FSClassLoader
> bundle, find the data directory for this bundle on the filesystem and find
> the associated files.
> I suggest we add a OSGi console for finding the associated .java files based
> on a script.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
