Do you know these features of Java Decompiler ?

Other than the basic “search for a word” and “go to line number”, following are some of the features of the latest Java Decompiler:

1. You can open multiple Jar files in tab. You can open multiple class files in tab. If one class has a reference to another class in the same jar, you can go to that class file by just clicking :

2. You can view the Type Hierarchy of a class file by selecting : Navigate –> Open Type Hierarchy ( F4 ) :

3. You can view the outline of the class ( methods and variables ) by selecting : Navigate –> Quick Outline ( Ctrl + Shift + O ) or you can click on the middle button of your mouse to open the quick outline :

4. It is possible to save a single class file as the Java source file and also to save all the class files in a jar as a zipped source file :

5. Copy and paste a stacktrace from a file into the Decompiler and the stacktrace became active in a clipboard window, provided the class files already opened in the Decompiler.

6. You can drag and drop and a set of JAR files into the Decompiler.

7. You can download the latest free version @ http://java.decompiler.free.fr/?q=jdgui and the eclipse plug-in @ http://java.decompiler.free.fr/?q=jdeclipse . Get the Eclipse 4.x version @ http://marketplace.eclipse.org/content/jadclipse-eclipse-4x

Comments

JBoss - know more about the JBoss directory structure

Fundamentally, the JBoss architecture consists of the JMX MBean server, the microkernel, and a set of pluggable component services - the MBeans. The JBoss Application Server ships with three different server configurations. Within the <JBoss_Home>/server directory, you will find three subdirectories: minimal, default and all. The default configuration is the one used if you don’t specify another one when starting up the server. If you want to know which services are configured in each of these instances, look at the jboss-service.xml file in the <JBoss_Home>/server/<instance-name>/conf/ directory and also the configuration files in the <JBoss_Home>/server/<instance-name>/deploy directory. JBoss 4.0 features an embedded Apache Tomcat 5.5 servlet container. conf --> The conf directory contains the jboss-service.xml bootstrap descriptor file for a given server configuration. This has the jboss-log4j.xml file which configures the Apach...

ATG Search and Search engine activity log

We could use the SearchEngineActivity log files to get the request/response to the search engine from a commerce instance. This folder is located in each commerce instance or the instances from which the call to the search engine is done. The SearchEngineActivity log file folder can be configured @ SearchEngineService component ( /dyn/admin/nucleus/atg/search/routing/SearchEngineService). To get the log files for the search engine calls, you need to specify the SearchEngineService.dumpingRequests as true. Then you need to specify the engineActivityPath as the folder in which you need the SearchEngineActivity logs. Below you could find my SearchEngineActivity log folder. Each successful call to the search engine from the commerce instance will create 5 files in the SearchEngineActivity folder : namely request, response, search engineinfo, stack trace and response row . Each file name start with a specific sequence. You ...

Search engine shutdown call from the Estore instnace

When the estore or commerce instances are restarted the routing system service can send shut down requests to stale engines, this can be caused because of any of the following. 1. Some other instance marked the engine as stopped in the DB (This can be caused because the machine could not reach the host running the engine) 2. The eStore instance is using a different search schema that has data about the search engine host and is marked as stopped in that DB. To avoid this overrride \atg\search\routing\RoutingSystemService.properties by setting cleanUpStrayEng=false.

How to simulate Browser back button

When someone asks how to simulate a back button, they really mean to ask how to create a link that points to the previously visited page. Most browsers tend to keep a list of which websites the user has visited and in what order they have done so. The DOM window object provides access to the browser's history through the history object. Moving backward and forward through the user's history is done using the back(), forward(), and go() methods of the history object. To move backward through history, just do window.history.back() ; This will act exactly like the user clicked on the Back button in their browser toolbar. Find below a sample html code: <html> <head> <script type="text/javascript"> function goBack(){ window.history.back() } </script> </head> <body> <input type="button" value="Back" onclick="goBack()" /> </body> </html>

ATG : Oracle started new discussion forum for ATG

Oracle has started a new ATG discussion forum on oracle discussion forums. It has a main ATG section and is divided into technical and business categories. You can access the url http://forums.oracle.com/forums/category.jspa?categoryID=503 . After Oracle acquired ATG, this was much expected and we can hope this forum might give us a better chance to discuss our ATG doubts and more people will come and discuss about ATG. Find the ATG docs @ http://www.oracle.com/technetwork/indexes/documentation/atgwebcommerce-393465.html

Tips from Sony Thomas

Search This Blog