Eclipse Indigo - good features of Eclipse3.7 ( Eclipse Indigo ) JDT/Workbench

Lightweight refresh on access

Previous Eclipse versions relied on native refresh providers (on Windows) or a polling mechanism to keep the workspace synchronized with the underlying file system. This capability can be still enabled by selecting Refresh using native hooks or polling on Preferences > General > Workspace.
Now a new lightweight mechanism is available. Files discovered to be out-of-sync by the workspace, for example while accessing the file content by an editor, will be automatically asynchronously refreshed. If you want to refresh files this way, go to Preferences > General > Workspace and select Refresh on access.

The Problems view icon shows state

The Problems view icon now indicates whether the view contains warnings or errors. This is especially useful when working with maximized editor area as it allows you to see whether there are errors or warnings without going to the Problems view.

Branch column in History view

There is now a column showing branches in the History view when using CVS.

Compare editor shows author on left side

The compare editors @ CVS now also show the author on the left side.

Undo support for breakpoints

If you accidentally removed a breakpoint from the editor's vertical ruler or the Breakpoints view, you can now get it back using the standard undo functionality - Edit > Undo Delete Breakpoint (Ctrl+Z) - in the Breakpoints view or any other view that works against the global undo history.

Open Super Implementation

The action from the Navigate menu is now also available as a hyperlink. It is enabled for overridden methods and opens the super implementation of the selected method.

Open Declared Type and Open Return Type

This link is enabled for local variables and fields. When invoked, it opens the declared type of the variable in an editor.

Join variable declaration" quick assist for variables initialized to null

The Join variable declaration quick assist is now also available for variables initialized to null.

New 'Put expression in parentheses' quick assist

The Java editor now offers a new quick assist Put expression in parentheses.

Semantic coloring for abstract classes

Abstract classes can now be highlighted separately in the source code @ Java- Editor - Synatax Coloring

Quick Outline shows inherited members for nested type

The Quick Outline shows inherited members of top-level types when Ctrl+O is pressed twice. Now, it also shows inherited members of the type that contains the current editor selection.

Navigate to 'break' and 'continue' target

To quickly navigate to the target of a break or continue statement, you can now Ctrl+click or use Open Declaration (F3) on break or continue keywords or their labels.

JDT Unavoidable generic type problems

It is really annoying to see warnings for things you cannot not change. A new compiler option has been added that suppresses unavoidable generic type problems.

Read more @ http://help.eclipse.org/indigo/index.jsp

Comments

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @ http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\s

ATG - quick reference to commonly used DSP Tags

In this blog, I would like to give a quick reference to the most commonly used DSP Tags.Note that in this DSP tag details : bean refers to a Nucleus path, component name, and property name param refers to a Page parameter value refers to a Static-value var refers to a EL variable id refers to a scripting variable ============================================================== 1.dsp:importbean example: <dsp:importbean bean="/atg/dynamo/droplet/Switch"/> ============================================================== 2.dsp:page usage: It encloses a JSP. The dsp:page invokes the JSP handler, which calls the servlet pipeline and generates HTTPServletRequest. example: <dsp:page> ..... </dsp:page> ============================================================== 3.dsp:include usage: Embeds a page fragment in a JSP. example: <dsp:include src="/myPage/ResultPage.jsp" flush="true">

GC Log Analyzer from IBM

This blog is about the GC( garbage collection) log analyzer from IBM. If you have a GC log and you want to analyze the file, this IBM tool will help you with some graphical analyzer and some recommendations. You can download it from the following URL : https://www.ibm.com/support/pages/ibm-pattern-modeling-and-analysis-tool-java-garbage-collector-pmat Please find below some screenshots and details that might help you. 1. Screenshot 1: 2. Screenshot 2 : 3. Screenshot 3 : 4. Screenshot 4:

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 could see that the file name like "2630436491482_

ATG Search - how to create a search project

Here I am going to explain how we can create a new ATG search project. It involves 3 steps --> Specify the general search project settings, Specify the content of search indexing and Build the index. Below I am elaborating the different steps involved with screen shots : 1. Go to Search Project Administration ui @ BCC and Click the button "New Search Project" to create a new search project. 2. Specify the search project name, give description and click the button "Create Search Project". 3. Click the button "Add Content" to add the search project content. 4. Specify the content name, select the content type and specify the IndexingOutputConfig path if the content type is ATG repository. Specify the remote host and port if you are using another server for fetching the content. 5. Click the content in the left side and expand the advanced option to specify the language and other customizations. 6. Click the

Tips from Sony Thomas

Search This Blog