Sunday, July 24, 2011

Onsite Opening for Java Professionals at Singapore

Job Location: Singapore

Dear Candidate,
We have excellent onsite opportunity for Java professionals with one of our leading client based in Chennai.

Candidate would be working at Singapore location.

Candidate should posses a valid passport.

Below are the details for the same :

Position : 10
Total exp - 4-6 years
Skills - Java J2ee
Domain - Banking domain
Location - Singapore
Job Type - Permanent
Joining time - 15-30 Days maximum

If interested, please mail me your resume asap to javaj2ee.dubai@gmail.com

Sunday, July 10, 2011

Java Developer - Job opportunity in Dubai

Dear Shakir,

If you have any of your friend with profile matching the job requirements stated below,

 kindly send us the latest CV for our review. 

Job requirement. 

 J2EE Skill Sets (minimum 4 years experience) 

 Springs, AJAX 

 Struts 

 JSP 

 ExtJS Components & Framework 

 iBatis 

 Hibernate 

 Strong in J2EE development. 

Also, furnish us the following details. 

- Current work location 

- No. of years of experience 

- Current CTC 

- Expected CTC 

- Earliest joining period (confirm if you are available in 2 weeks) 

- Marital Status 

- Contact Numbers (Home, Mobile) 

Your immediate response will be much appreciated. 

Thanks & regards, 

Bst Rgds,
Mohammed Shakir

( Congratulations!!! Reach out to the Whole New Internet Generation. Now Promote your Business on my Blog - Please email me for availing New Advertisement Services !!!)

"Watch your thoughts; they become words. Watch your words; they become actions. Watch your actions; they become habits. Watch your habits; they become character. Watch your character; it becomes your destiny."

Quran [2:216]  But you may dislike something which is good for you, and you may like something which is bad for you. GOD knows while you do not know.

http://shawnetv2.shawgrp.com/weekly/PublishingImages/GoGreenIcon_rev1.gifLove Nature...
 Save a tree. Use Less Papers. Don't print this e-mail unless it's really necessary!!

Saturday, July 2, 2011

Java - J2ME - DICETECK LLC - Dubai - United Arab Emirates

- 3+ Years of experience in Java/J2EE/J2ME technology. 
Proficient in Canvas, Graphics, and UI design
Proficient in developing J2ME applications using CLDC 1.1, MIDP 1.0/2.0/2.1, NETBEANS/ECL
- Must have good knowledge different APIs, JSRs, 
- Have thorough understanding (at low level) of different channels like SMS, GPRS, USSD
- Must be well versed with using PKI, Secure Elements available in SIM or NFC
- Well versed with latest mobile trends and technologies (NFC, TSM, Mobile Wallet, Location based Advertising, maps, Coupons, mobile POS)
- Plus to have knowledge of different devices and their SDKs/Emulators like Blackberry, Symbian, AndroidiPhoneWindows
- A quick learner of new technologies and ready to switch between different technologies

If your profile is suitable please email your profiles to reshmi@dicetekuae.com

Bst Rgds,
Mohammed Shakir

( Congratulations!!! Reach out to the Whole New Internet Generation. Now Promote your Business on my Blog - Please email me for availing New Advertisement Services !!!)

"Watch your thoughts; they become words. Watch your words; they become actions. Watch your actions; they become habits. Watch your habits; they become character. Watch your character; it becomes your destiny."

Quran [2:216]  But you may dislike something which is good for you, and you may like something which is bad for you. GOD knows while you do not know.

Love Nature...
 Save a tree. Use Less Papers. Don't print this e-mail unless it's really necessary!!

Wednesday, June 15, 2011

Eclipse and MAC OS - A Natural Combination

Why Do Java Development on the Mac?

The ease of use of Mac OS X, the power and stability of UNIX, the integration of Java into Mac OS X and the availability of great development environments like Eclipse make the Mac a great Java development environment.
UNIX users feel at home in Darwin, the robust UNIX-based environment that underlies Mac OS X. That environment is accessible at any time from the Terminal application. All of the standard UNIX utilities and scripting languages are included in Mac OS X—editors such as emacs, vim and pico; file management tools such as cp, mv, ls and gnutar; shell scripts including bash, tcsh (csh) and zsh; and scripting languages such as Perl, PHP, tcl, Ruby and Python. For Java-based web engineers, Apache, Tomcat and JBoss are also included, so you can do JSP development or enterprise class J2EE applications.
Mac OS X also gives you a highly mobile platform. The PowerBook series provides a high-powered workstation that is completely portable and allows you to pick up and go, and then quickly resume work at a new location. Even as you open your laptop, network connections are being reestablished and the computer is immediately up and running.
Apple has made Java a core component of Mac OS X—every Mac ships with the full version of Java 2, Standard Edition included—meaning you have the Java Developer Kit (JDK) and the HotSpot virtual machine (VM) without downloading, installing or configuring anything. And because Apple has optimized Java on Mac OS X, Java applications act as first-class citizens on Mac OS X.
In addition to Eclipse many of the industry leading tools are available, including IntelliJ's IDEA, Borland's JBuilder, Oracle's JDeveloper, and Sun's NetBeans, just to name a few. Mac OS X also includes free developer tools which support rapid Java development right out of the box.

Getting Started

You can get a copy of Eclipse by visiting the Eclipse download page and downloading the latest build. (The current version of Eclipse requires Mac OS X v10.3 Panther.) All builds are delivered as .ZIP files.

Download and install Eclipse

  1. Using your Safari browser, go to the eclipse.org Website.
  2. Click Downloads.
  3. Click Main Eclipse Download Site. If you are not located in North America, use the mirror site closet to your location.
  4. Click the name of the Release Build you want. At the time of this writing, the "3.0 Stream Stable Build" is the latest developer preview of version 3.0. This version is currently fine for daily use.
  5. Under "Eclipse SDK, find "Mac OSX (Mac/Carbon) (Supported Versions)"—the file name is also displayed. Select either the HTTP or FTP download option.
  6. After reading the Notes, click "Download" at the bottom of the page.
  7. When the download is complete, unzip the archive into the appropriate folder.
    (Older versions of Stuffit truncated file names and caused problems with Eclipse. Make sure you are using the appropriate version.)

    Your installation is now complete.
  8. Click the Eclipse icon to launch the IDE.
The first time you run Eclipse, it completes a few remaining install tasks—such as creating a workspace directory—before the Eclipse environment appears.

Work through the tutorials

With Eclipse installed and running, you can begin by looking at an overview of Eclipse features and plugins installed on your system, and then doing a tutorial that guides you through building a simple Java application.
To see the overview of the Eclipse features: from the Help menu, choose About Eclipse Platform
To do a tutorial on building a simple Java application: from the Help menu, choose Java Development User Guide > Getting Started > Basic Tutorial

Resources for More Information

Maven in 5 Minutes

Maven in 5 Minutes


Maven is a Java tool, so you must have Java installed in order to proceed.
First, download Maven and follow the installation instructions. After that, type the following in a terminal or in a command prompt:
mvn --version
It should print out your installed version of Maven, for example:
Maven version: 2.0.8
Java version: 1.5.0_12
OS name: "windows 2003" version: "5.2" arch: "x86" Family: "windows"
Depending upon your network setup, you may require extra configuration. Check out the Guide to Configuring Maven if necessary.

Creating a Project

On your command line, execute the following Maven goal:
mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false
If you have just installed Maven, it may take a while on the first run. This is because Maven is downloading the most recent artifacts (plugin jars and other files) into your local repository. You may also need to execute the command a couple of times before it succeeds. This is because the remote server may time out before your downloads are complete. Don't worry, there are ways to fix that.
You will notice that the generate goal created a directory with the same name given as the artifactId. Change into that directory.
cd my-app
Under this directory you will notice the following standard project structure.
|-- pom.xml
`-- src
    |-- main
    |   `-- java
    |       `-- com
    |           `-- mycompany
    |               `-- app
    |                   `-- App.java
    `-- test
        `-- java
            `-- com
                `-- mycompany
                    `-- app
                        `-- AppTest.java
The src/main/java directory contains the project source code, the src/test/java directory contains the test source, and the pom.xml is the project's Project Object Model, or POM.


The pom.xml file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <name>Maven Quick Start Archetype</name>

What did I just do?

You executed the Maven goal archetype:generate, and passed in various parameters to that goal. The prefix archetype is the plugin that contains the goal. If you are familiar with Ant, you may conceive of this as similar to a task. This goal created a simple project based upon an archetype. Suffice it to say for now that a plugin is a collection of goals with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".

Build the Project

mvn package
The command line will print out various actions, and end with the following:
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Oct 05 21:16:04 CDT 2006
[INFO] Final Memory: 3M/6M
[INFO] ------------------------------------------------------------------------
Unlike the first command executed (archetype:generate) you may notice the second is simply a single word - package. Rather than a goal, this is a phase. A phase is a step in the build lifecycle, which is an ordered sequence of phases. When a phase is given, Maven will execute every phase in the sequence up to and including the one defined. For example, if we execute the compile phase, the phases that actually get executed are:
  1. validate
  2. generate-sources
  3. process-sources
  4. generate-resources
  5. process-resources
  6. compile
You may test the newly compiled and packaged JAR with the following command:
java -cp target/my-app-1.0-SNAPSHOT.jar com.mycompany.app.App
Which will print the quintessential:
Hello World!

Running Maven Tools

Maven Phases

Although hardly a comprehensive list, these are the most common default lifecycle phases executed.
  • validate: validate the project is correct and all necessary information is available
  • compile: compile the source code of the project
  • test: test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed
  • package: take the compiled code and package it in its distributable format, such as a JAR.
  • integration-test: process and deploy the package if necessary into an environment where integration tests can be run
  • verify: run any checks to verify the package is valid and meets quality criteria
  • install: install the package into the local repository, for use as a dependency in other projects locally
  • deploy: done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.
There are two other Maven lifecycles of note beyond the default list above. They are
  • clean: cleans up artifacts created by prior builds
  • site: generates site documentation for this project
Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, packageexecutes jar:jar if the project type is a JAR, and war:war is the project type is - you guessed it - a WAR.
An interesting thing to note is that phases and goals may be executed in sequence.
mvn clean dependency:copy-dependencies package
This command will clean the project, copy dependencies, and package the project (executing all phases up to package, of course).

Generating the Site

mvn site
This phase generates a site based upon information on the project's pom. You can look at the documentation generated under target/site.


We hope this quick overview has piqued your interest in the versitility of Maven. Note that this is a very truncated quick-start guide. Now you are ready for more comprehensive details concerning the actions you have just performed. Check out the Maven Getting Started Guide.


Friday, February 25, 2011

The Do’s and Don’ts of Phone Interviews

Phone interviews are common and often used to screen out potential candidates before being called for the in-person interview. These are also used when the candidates live in another city or country. When you have applied for a job, you need to be prepared for the phone interview. Phone interviews can be different from in-person interviews in certain respects so a few points need to be kept in mind when preparing for the phone interview.

Keep a record of the time and date
Make sure you do not forget the time or date when the interview is scheduled and keep yourself free from any other appointments at that time.

Do your homework
Find out some basic information about the role and company you have applied to. It is very common for the interviewers to find out how much information you have about the company and the particular you have applied for. It shows your interest level in the job. Prepare for the questions just like you would for an in-person interview.

Avoid the use of cell phone
Try to have the interview conducted on a landline instead of a cell phone. This is because chances of network failures and line disturbances will be reduced this way.

Choose an appropriate location
It seems highly unprofessional if there is a lot of background noise while you are being interviewed. Choose a quiet and private location, keep the doors and windows closed, and make sure the children and pets are kept out.

Focus on gestures
Even though you are not face to face with the interviewer, do smile when answering the questions as it can help to improve the tone of your voice and keep you more calm. Do not chew gum, smoke a cigarette, eat or drink during the phone interview. Speak clearly and enunciate properly.

Tuesday, February 1, 2011

10 Steps to Become an Outstanding Java Developer

If you are a Java developer and passionate about technology, you can follow these ten points which could make you an outstanding Java developer.

1. Have strong foundation and understanding on OO Principles
For a Java developer, having strong understanding on Object Oriented Programming is a must. Without having a strong foundation on OOPS, one can't realize the beauty of an Object Oriented Programming language like Java. If you don't have good idea on what OOPS is, even though you are using OOP language you may be still coding in procedural way. Just studying OO principle definitions won't help much. We should know how to apply those OO principles in designing a solution in OO way. So one should have a strong knowledge on Object modeling, Inheritance, Polymorphism, Design Patterns.

2. Master the core APIs
 It doesn't matter how strong you are in terms of theoretical knowledge if you don't know the language constructs and core APIs. In case of Java, one should have very strong hands-on experience with core APIs like java.lang.*, I/O, Exceptions, Collections, Generics, Threads, JDBC etc. When it comes to Web application development, no matter which framework you are using having strong knowledge on Servlets, JSPs is a must.

3. Keep coding
Things look simpler when talking about them theoretically. We can give a solution to a problem very easily in theory. But we can realize the depth of the problem when we start implementing our approach. You will come to know the language limitations, or design best practices while coding. So keep coding.
4. Subscribe to forums
We are not alone. There are lots of people working on the same technologies that we are working on. While doing a simple proof of concept on a framework may not give you real challenges, when you start using it on real projects you will face weird issues and you won't find any solution in their official documentation. When starting to  work on a new technology the best and first thing to do is subscribe to the relevant technology forums. Whatever the issue you are facing, someone else in the world might have already faced it earlier and might have found the solution. And it would be really really great if you can answer the questions asked by other forum users.

5. Follow blogs and respond
As I already told you are not alone. There are thousands of enthusiastic technology freaks around the world blogging their insights on technology. You can see different perspectives of same technology on blogs. Someone can find great features in a technology and someone else feels its a stupid framework giving his own reasons of why he felt like that. So you can see both good and bad of a technology on blogs. Follow the good blogs and respond/comment on posts with your opinion on that.
6. Read open source frameworks source code
A good developer will learn how to use a framework. But if you want to be an outstanding developer you should study the source code of various successful, popular frameworks where you can see the internal working mechanism of the framework and lot of best practices. It will help a lot in using the frameworks in very effective way.
7. Know the technology trends
In the open source software development technology trends keep on changing. By the time you get good idea on a framework that might become obsolete and some brand new framework came into picture with super-set of features. The problem which you are trying to solve with your current framework may be already solved by the new framework with a single line of configuration. So keep an eye on whats coming in and whats going out.
8. Keep commonly used code snippets/utilities handy
Overtime you may need to write/copy-paste same piece of code/configuration again and again. Keeping those kind of configuration snippets like log4.properties, jdbc configuration etc and utilities like StringUtils, ReflectionUtils, DBUtils will be more helpful. I know it itself won't make you outstanding developer. But just imagine some co-developer asks you to help in fetching the list of values of a property from a collection of objects and then you just used your ReflectionUtil and gave the solution in few minutes. That will make you outstanding.
9. Know different development methodologies
Be familiar with various kinds of methodologies like Agile, SCRUM, XP, Waterfall etc. Nowadays choosing the development methodology depends on the client. Some clients prefer Agile and some clients are happy with waterfall model. So having an idea on various methodologies would be great.
10. Document/blog your thoughts on technology
In day to day job you may learn new things, new and better way of doing things, best practices, architectural ideas. Keep documenting those thoughts or blog it and share across the community. Imagine you solved a weird problem occurred while doing a simple POC and you blogged about it. May be some developer elsewhere in the world is facing the same issue on a production deployed application. Think how important that solution for that developer. So blog your thoughts, they might be helpful for others or to yourself.

From : http://sivalabs.blogspot.com/2011/01/10-things-to-become-outstanding-java.html