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

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag. <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top"> <p>Name: <dsp:input bean="/samples/Person.name" type="text"/> <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/> <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/> </dsp:form> When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...

ATG CA - BCC home screen : how to add a new link

Activity source is the property which controls the links on the left nav on the BCC home screen. All activity sources are registered with the ActivityManager component at /atg/bizui/activity/ActivityManager . When rendering the BCC home page, the ActivityManager cycles through all the registered ActivitySource components and displays left navigation links for each of them on the BCC home page. For example if I want to add a new link "My New Link" , below screen shots exaplins how this can be done 1. Add activityManager.properties to specify the activityresources. In this activityManager, I specified one MyActivitySource. 2. Add MyActivitySource.properties to specify the name of the link and the other details . Here it refers to a bundle properties file. 3. Add the bundle properties file to specify the name of the link. 4. Now you could see the new link...

ATG Search architectural flow : Search and Index

I would like to explain the high level ATG Search implementation architecture ( for an online store) through the above diagram. In this diagram 1.x denotes the search functionality and 2.x denotes the indexing functionality. I have given JBoss as the application server. Physical Boxes and Application Servers in the diagram ( as recommended by ATG ) : Estore ( Commerce ) Box --> The box with the estore/site ear (with the site JSPs and Java codes). Search Engine Box --> The box with the search engine application running. Indexing Engine Box --> The box with the indexing engine application running. CA (Content Administration) Box --> The box with the ATG CA ear ( where we could take CA -BCC - Search Administration and configure the search projects) . Search Indexer Box --> The box with the ATG Search Index ear ( to fetch the index data from repository). Note that the engine performing indexing will need access ...

ATG Search - search engine tuning settings

In this blog, I am going to list the best tuning settings for ATG Search engine. The AESoapConfig.xml, AESoapWaspConfig.xml and AEConfig.xml are the xmls referred below and you can find it @ <ATG_DIR>\<Searchx.x>\SearchEngine\<operating_system>\bin\ folder. (1) Make sure that the AESoapConfig.xml's rwTimeout is less than or equal to routing's readTimeoutMs. You could find the routing's readTimeoutMs @ atg\search\routing\SearchEngineService component. rwTimeout is the length of time in seconds to wait before a read or write operation times out on an active connection. The number can be decreased to improve performance. However, a value that is too low could cause slow connections to be prematurely closed. (2) Adjust the number of engine threads to match the number of CPUs available to the engine. Note that the minimal value for maxThreads and maxSpar...

ATG Search Indexing - overview of different steps in search indexing

Read more about the search indexing behind the scene steps @ http://tips4ufromsony.blogspot.in/2011/12/atg-search-indexing-behind-scene-steps.html ATG Search prepares searchable content by indexing the products specified in the XML definition file (/atg/commerce/search/ProductCatalogOutputConfig). Generally there are two types of indexing 1. Full Indexing --> all data taken for indexing 2. Incremental Indexing --> only changed data will be taken for indexing When full indexing is triggered, following happens: 1. The out of box component BulkLoader will call IndexedItemsGroup.getGroupMembers() to load the products to the XHTL document. It prevents uncategorized products from getting indexed. The definition file format begins with a top-level item as a product and includes the properties of parent category and childskus. For each product, the set of Variant Producers configured in ProductCatalogOutputConfig is execute...

Tips from Sony Thomas

Search This Blog