Well, this is a very handy and important note as this will help overcome many issues and errors.
Whenever we get CLASSCASTEXCEPTIONS, FILENOTFOUNDEXCEPTION, LINKAGEERROR etc with APIs we need to know which jar contains those APIs so that we can juggle those jars and thereby resolve the issues.
If you are looking for a class which is not present on your machine the best place to find and download is
1>
http://www.findjar.com
Simply paste the API in the textbox and Click on "JAR/Class Search" button.
2>
If you wish to track the API on your existing system.
Kindly download the tool [JavaClassFinder.exe] from the link below.
JavaClassFinder.rename
or
http://mohtashims.files.wordpress.com/2010/07/javaclassfinder-rename.doc
Ener the API and the patch where you want the tool to search for the API.
Note: It is a 30 day evaluation, aftre which it would expire.
3>
If you wish to track the API on your existing system.
This tool [jarscan.jar] is similar to "JavaClassFinder" however it has a pro and a con.
Con: It does not have a GUI. It is command line.
Pro: Its is free
Steps to use it.
a) Download scanjar from the link below.
http://mohtashims.files.wordpress.com/2010/07/jarscan-jar.doc
b> Open a command prompt [Run- > cmd - Enter key] / comand line and set the JVM environment
c> Execute the following command.
java -jar jarscan.jar -dir D:\BEA1001 -package weblogic.security.service -class SubjectManagerImpl
where "D:\BEA1001" is the patch where you wish to search for the API.
"weblogic.security.service" is the package name of the API.
"SubjectManagerImpl" is the name of the Class not found.
If the output is too lengthy, kindly direct the output to some text file.
For example:
java -jar jarscan.jar -dir D:\BEA1001 -package weblogic.security.service -class SubjectManagerImpl >output.txt
"output.txt" will be generated in the present directory in which you are currently in.
No comments:
Post a Comment