Skip to main content

Good features of Eclipse3.5 (Eclipse Galileo) JDT


This blog will list down the new features of Eclipse Galileo JDT. I will write another blog regarding the features of Eclipse Helios and Eclipse Indigo.

Read about Eclipse Helios features @ http://tips4ufromsony.blogspot.com/2011/11/good-features-of-eclipse-36-eclipse.html

==========================================================
1. Toggle Breadcrumb —> Will list the name of the file and the method name with respect to your cursor position , on the top of the Eclipse IDE. From here you can go to other methods, other classes in same package , ….

Screen shot of Toggle Breadcrumb:



==========================================================
2. From the method call , you can either go to declaration or to implementation

Screen shot of implementation call:



==========================================================
3. Advanced Open Type –> You can restrict the open type to a selected Working set only.

Screen shot of Advanced Open Type:



==========================================================
4. Embedded Telnet connection window —> You can have the telnet connection as a window in Eclipse

Screen shot of Telnet connection:



==========================================================
5. Embedded Sql developer —> You can view the database tables , run queries , can see the history of queries ran and the results …

Screen shot of Sql Developer:



==========================================================
6. Enhanced Local History —> You can view all the changes that you made in a file in all the file save that you done. —> Just like clear case/SVN / CVS , you can compare with the previous versions of the files to see each line changes

Screen shot of Enhanced Local History:



==========================================================
7.A new property window to view the properties of the selected file

Screen shot of property window:



==========================================================

8.Exclude selected packages or files from the build path

Screen shot of Exclusion of build path:



==========================================================
9. Ctrl +3 —> Advanced quick access to the available screens by typing the start letters

Screen shot of Ctrl +3:



==========================================================

10. XML files can be open in a Design View

Screen shot of XML Design View:



==========================================================

11. Quick search in window – Preference

Screen shot of  Quick search in window – Preference:



Comments

  1. Good materials to learn the features. We started using the Eclipse Indigo...waiting for the blog on that :-)

    ReplyDelete
  2. Thank you Legin, will update you guys regarding the Eclipse Helios and Eclipse Indigo.

    ReplyDelete

Post a Comment

Popular posts from this blog

Eclipse plug-in to create Class and Sequence diagrams

ModelGoon is an Eclipse plug-in avaiable for UML diagram generation from Java code. It can be used to generate Package Dependencies Diagram, Class Diagram, Interaction Diagram and Sequence Diagram. You coud get it from http://marketplace.eclipse.org/content/modelgoon-uml4java Read more about it and see some vedios about how to create the class and sequence diagram @ http://www.modelgoon.org/?tag=eclipse-plugin Find some snapshots below which gives an idea about the diagram generation.

ATG - basic concepts of ATG

This blog is for the ATG beginners to get some basic overview about ATG. I just given the ATG concepts as a list of numbered points for the ease of understanding. 1. At the framework level, ATG is a               java based application platform for hosting web-based applications, as well as RMI accessible business components,               with an ORM layer,               a component container,               an MVC framework,               and a set of tag libraries for JSP. 2. Art Technology Group(ATG)'s Dynamo Application Server (DAS) is a Java EE compliant application server. DAS is no longer actively developed as ATG recommends using other Java EE applications servers for its products such as BEA WebLogic, JBoss or IBM WebSphere. 3. Prior to ATG 2007, JHTML was used instead of JSP for view purpose. J...

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

JBOSS How to change the default HTTP port 8080

To change the default HTTP port 8080, you need to edit the “jboss-service.xml” (<jboss>\server\<application>\conf\jboss-service.xml). In your “jboss-service.xml” ,search for the mbean ServiceBindingManager. It will be commented by default. You can uncomment it. It is referring to a sample xml port binding file in the example folder ( ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml ). You can either use this xml or copy it to another location and give that path in your “jboss-service.xml”. In the sample-bindings.xml,  search for the <server name=”ports-01?> ( as given in your “jboss-service.xml” ) . In this “server name” , search for the “service-config” with <delegate-config portName=”URLPort”/> for the “type=HTTP” and change the port to <binding port=”8180?/> to use 8180 instead of 8080.