[Smartfrog-checkins] [Smartfrog.org-JIRA] Created: (SFOS-927) improve diagnostics on ClassNotFoundExceptions

[Steve L. (JIRA) <ji...@sm...>]

improve diagnostics on ClassNotFoundExceptions
----------------------------------------------

                 Key: SFOS-927
                 URL: http://jira.smartfrog.org/jira/browse/SFOS-927
             Project: SmartFrog
          Issue Type: Improvement
          Components: .sfCore
            Reporter: Steve Loughran
            Assignee: Julio Guijarro
            Priority: Minor


Because the JVM is so uninformative on ClassNotFoundExceptions, when there is trouble with classpaths, much time can be wasted tracking down the problem.

1.  PrimImpl could handle such exceptions by adding in lots more diagnostics.
2., we have a org.smartfrog.services.os.java.LoadClassImpl class to help, but even its diagnostics can be improved. 
3. we could have a command line command that could deploy a LoadClass instance to test that a class is present

some ideas for better diagnostics

-Look for the resource, using ClassLoader.findResource() to get (and print) the URL of the .class file -and flagging if that file does not exist
-Advanced: look inside the .class file and get the list of imported classes, then look for every such imported class. This can track down (some) missing dependencies, but is not enough for dependencies of parent/constructed classes.



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