Eclipse Juno - good features of Eclipse 4.2 ( Eclipse Juno ) JDT/Workbench

Global search bar

The workbench now has a global search field in the tool bar.

Multi-drag sash

You can now place the cursor at the intersection of two or more sashes and drag them all at the same time. When you are going to be dragging multiple sashes, the cursor will change to one with 4-way arrows. The image below indicates one such intersection with a red circle.

Ant updated to 1.8.3 and JUnit to 4.10

The bundled version of Apache Ant in the platform has been updated to version 1.8.3. The JUnit 4 version shipped with Eclipse has been updated to 4.10.

CamelCase in Quick Outline

The Quick Outline (Ctrl+O) and Quick Hierarchy (Ctrl+T) in the Java Editor now also support camelCase matching on the element name, quite similar to the Open Type dialog and Content Assist.

Quick Assist to convert enhanced for loop

Ever encountered an enhanced for loop and needed access to the Iterator or to the loop index? Now, you can just use a Quick Assist (Ctrl+1) to convert the loop.

Improved bracket matching support in Java editor

The Java editor now supports highlighting of enclosing brackets.

New options to detect resource leaks

The compiler can now detect leakage of resources i.e. local variables of type java.lang.AutoCloseable (compliance >= 1.7) and java.io.Closeable (compliance <= 1.6).

For more details, please check http://help.eclipse.org/juno/index.jsp

Comments

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties : This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties : After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...

ATG Search - how to define the search configuration rules

ATG Search configuration rules are specified through the ATG BCC Merchandising UI. Over here you could specify the below set of rules Redirection rules --> If you want to redirect to another page other than the search result page for a search keyword Property Prioritization rules --> Prioritize certain set of properties and give weightage Result exclusion rules --> Exclude certain search results Result positioning rules --> Position / Sort the search result data 1. To create the search configuration tree, you need to log-in to the ATG BCC Merchandising UI and select the Search Configuration Tree in the Browse tab drop down. Now need to click the Create button and first you need to create the Search Configuration Folder. 2. When you create the folder, give the name of the folder and select whether the contents vary by Language or Segment. If your ecommerce site need to support more than one language and y...

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/Result...

ATG Search Indexing - behind the scene steps explained

Read more about the search indexing @ http://tips4ufromsony.blogspot.com/2011/11/atg-search-architectural-flow-search.html ATG search indexing involves index file creation, deploying and copying the index file to the search engine's box. The steps can be divided into Initial stage, Preparing Content, Indexing and Deploying. Please find below the detailed analysis of each step. 1. Initial stage: a. Check whether the folder deployshare configured correctly @ LaunchingService.deployShare ( \atg\search\routing\LaunchingService.deployShare ). Lets assume that it is configured to \Search2007.1\SearchEngine\i686-win32-vc71\buildedIndexFiles. b. Lets assume that the index file folder ( \Search2007.1\SearchEngine\i686-win32-vc71\indexFiles) has the following segments (folders) currently : 66900...

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...

Tips from Sony Thomas

Search This Blog