configure jadclipse in eclipse platform

-
download the zip file jad158.zip,This can  be downloaded from the following link.

Java Decompiler

extract the zipfile to verify the files 'net.sf.jadclipse_3.3.0.jar' and 'jad.exe' are present.

copy the net.sf.hadclipse_3.3.0.jar to the working copy of your eclipse plugin folder.

open your eclipse goto  Window->Preferences,Expand the Java Tab,now you will see the JadClipse option.

click on the 'JadClipse' option tab,you may find two fields.set the values as below.

1. Path to decompiler to your jad executable location
   (eg D:\workspace\setup\JAD\jad158.exe).
2. Directory for temporary files to  any desired folder(eg
   D:\workspace\setup\JAD).

Click Apply,Ok and Restart your Eclipse,done !!!

Now press F3 button on the class to view the source for that class.


Configure JUnit

Download the junit-4.10.jar file from the location  and add this file in the java build path on the Eclipse Project where we want to configure the Junit.



After you configured the build path,restart your workspace and you will see an option like below to run the JUnit test cases.



 For Creating method stubs you need to right click on the respective Java File ,New-JUnit Test Case.Give a name with a suffix 'test' preferably,click 'Next' , you can see a list of methods in the actual class select the checkbox for corresponding methods you want to create stubs and click 'Finish'.

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more