scribbles of the perennial debugger…
Posts tagged Eclipse
get Eclipse Dali, quick!
Nov 23rd
I’ve seen the evils and the necessity of OR Mapping. Many people toyed with different persistence mechanisms. Entity Beans (heck no for me), JDO, SDO, open source mappers such as Hibernate, proprietary OR Mappers such as TopLink, etc. None of which intrigued me most but Java EE’s JPA. JPA allows for a transparent OR Mapping facility. The name of the game is Standards. By adhering and using only standard JPA api, you could toy around with different OR Mapping implementations that supports JPA without modifying your code. You might choose Hibernate as your underlying mapper, but later on, you can change that to TopLink or Kodo in a jiffy. No source code change. Well of course, you need to re-map according to your new mapper’s constructs.
Humming JPA, here comes Dali from Eclipse.
The goal of the Dali JPA Tools Project is to build extensible frameworks and exemplary tools for the definition and editing of Object-Relational (O/R) mappings for EJB 3.0 Java Persistence API (JPA) Entities. JPA mapping support will focus on minimizing the complexity of mapping by providing creation and automated initial mapping wizards, and programming assistance such as dynamic problem identification.
I have been pushing for our internal OR Mapper a.k.a. DAO to be upgraded to JPA compliance. It is either we adapt the JPA interfaces, or… use JPA from within. OK boss, what’s your pick. But until then, just keep dreaming…
I Have A New Toy
Aug 31st
Repost from Randomized!
====
I just installed Eclipse 3.1. What a breeze. The time it took me to install was 10 times faster that the time it took me to download.
I am really excited in trying out the new features in this IDE. So much for the NetBeans 4.1 crap. Now let me see… I have JDK 5, I have Eclipse 3.1. I have a java source to work with. What else… ahh! I am still using FC3. Anyways, this post is not about Fedora.
The cool stuff about Eclipse 3.1 is speed. All about speed. Since I mix up between CLI activity and GUI IDE activity, my old Eclipse 3 was just as handy. But with hundreds of codes that I work with, auto-compilation grinds to a standstill when I refresh or even introduce a new java source.
Let me see later whether VE (visual editor) is already up to the task. I dropped using this in favor of NetBeans because VE is a crap. *sigh* If only I could extract the GUI builder part of NetBeans and make it as a stand-alone kick-start utility, then I would the best utilities a java developer can ask for.
My new toy:
Eclipse 3.1
Aug 31st
A repost from my Randomized! blog. So far Eclipse 3.1 has been a wonderful toy to play with.
==========
Eclipse 3.1 is Out!
It has been a while since fanatics waited (since June 25, 2004) for the next version of their beloved Eclipse IDE. What’s new and noteworthy about this new release is that many woes and supposed-to-have from Eclipse 3.0 has been resolved.
Some of this blog’s text are excerpts from eclipse.org
Significant Performance Enhancements – thank goodness!
Support for bi-directional text – naah! I would not have any use for this. My stand is that since Java language is an English derivative, text and text orientation should be inherently english too.
Improved preferences and properties support – nice goodies!
Editor lookup based on content type – not so usable to me since I have been a VI baby…
Importing multiple projects – not so usable to me either…
Line delimiter support – not so usable to me either since I only work with Linux/Unix
Single JAR plug-ins – aha! nice way to remove unwanted plugins!
New JDT Goodies – these will certainly improve my productivity ten-folds
* New Javadoc compiler settings
* Serial Version UID
* Early detection of references to internal classes
* Access rules on libraries and projects
* Mark occurrences of inherited methods
* Highlighting of deprecated class members in the Java editor
* References in Javadoc
* Improved Java properties file editor
* Working with externalized strings
* Externalize Strings wizard supports new message bundles
* New Open Type dialog
Full support for J2SE 5.0 – and yes!!! The Tiger Roars!!!!
Eclipse 3.1 includes full support for the new features of J2SE 5.0. This support is both pervasive and powerful — everything that you expect to work with J2SE 1.4, including editing, code assist, compiling, debugging, quick fixes, refactorings, source actions, searching, etc. will work seamlessly with (and has been extended to support the new capabilities of) J2SE 5.0′s new types and syntax.
Here are some examples:
* Quick Fix to update JRE and compiler compliance to 5.0
* New Type wizards support generics
* Enumeration and Annotation wizards
* Semantic coloring of J2SE 5.0 constructs in Java editors
* Rename refactorings handle renaming of type parameters
* Infer Generic Type Arguments refactoring
* Quick fixes for Generics
* Search result filters for reference search for parameterized types
* Code completion for annotations
* @SuppressWarnings annotation support
* optional diagnoses for issues such as incomplete enum switches and boxing/unboxing conversions
* Quick Fix to create enum constants
* Autoboxing parameter proposals
* Quick Assist to convert for-loops over arrays and collections to J2SE 5.0 enhanced for-loops
* Support for package-info.java
Eclipse 3.1 release is now available for download from the eclipse.org downloads page. Go get it!