Google
 

Wednesday, March 16, 2011

Google Code Jam Africa and Arabia 2011

If you're interested in getting a cool Prize or being considered for an internship at Google Zurich, then you should register and compete in "Google Code Jam Africa and Arabia 2011"

Location: Online
Schedule: http://code.google.com/codejam/africa_arabia/schedule.html
More details: http://code.google.com/codejam/africa_arabia


Source

Tuesday, March 15, 2011

Business Analyst and Systems Analyst – THEY ARE DIFFERENT

This week I received another request from a recruiter seeking a person to fill a vacant Business Analyst (BA) position. In my role as coordinator of the Australian Computer Society IT Contractors and Consultants Special Interest Group I am often asked by recruiters if I know of any people who are currently looking for work. During the dark days of the dot com bust my answer was always yes, however today (thankfully) my answer is often no.

My approach when I receive a request from a recruiter is to examine some of the details of the role. This helps me in identifying possible candidates. During this examination I am continually amazed about the confused nature of the BA role. The role definition is often a confusing set of requirements which span across technical and non technical areas.
It is not uncommon for a BA role definition seeking detailed knowledge of J2EE or .Net. Sometimes programming skills are mentioned as very desirable. I am often left wondering do they want a Business Analyst or a Systems Analyst.

The term “Systems Analyst” seems to have fallen out of favor in the last 5 years or so, but I don’t think the requirement has gone away. Business Analysts and System Analysts are different roles. They perform very different functions during the software development life cycle. Both roles are needed and both are very important.

The Systems Analyst role attempts to provide a bridge between the business requirements and the technical definition of the IT solution. The Business Analyst role is primarily about documenting and gathering the business requirements. The important point to note that the two roles are complimentary, you need both to make a successful IT project.

Source

Monday, February 8, 2010

Java Developer Conference 2010

Java Developer Conference 2010

I think this year's JDC will be so great and so interesting.

Do not miss the chance to attend.

Sunday, May 10, 2009

My Programmer Personality Type is -- PHTB

I tried the " Programmer Personality Type" test and following is my detailed result:

Your programmer personality type is:

PHTB

You're a Planner.
You may be slow, but you'll usually find the best solution. If something's worth doing, it's worth doing right.


You like coding at a High level.
The world is made up of objects and components, you should create your programs in the same way.


You work best in a Team.
A good group is better than the sum of it's parts. The only thing better than a genius programmer is a cohesive group of genius programmers.


You are a liBeral programmer.
Programming is a complex task and you should use white space and comments as freely as possible to help simplify the task. We're not writing on paper anymore so we can take up as much room as we need.

To try the test yourself, go to the following link:

Programmer Personality Test

Good Luck

Saturday, September 13, 2008

Streaming API for XML

Many people are working with web services. Thus, web services is an evolving field that always has new terchnologies and/or APIs to support and ease the way to developing and using web services.


I am introducing here a java API that is supposed to be one of those evolving APIs that help enhance the work with web services and also enhance the work of web services themselves. Actually, I have known about it from a colleague of mine and found it interesting and worth learning about. That is StAX which stands for "Streaming API for XML". StAX is a streaming Java-based, event-driven, pull-parsing API for reading and writing XML documents. StAX enables you to create bidrectional XML parsers that are fast, relatively easy to program, and have a light memory footprint.

StAX is the latest API in the JAXP (Java API for XML Processing) family, and provides an alternative to SAX, DOM, TrAX, and DOM for developers looking to do high-performance stream filtering, processing, and modification, particularly with low memory and limited extensibility requirements. 

To summarize, StAX provides a standard, bidirectional pull parser interface for streaming XML processing, offering a simpler programming model than SAX and more efficient memory management than DOM. StAX enables developers to parse and modify XML streams as events, and to extend XML information models to allow application-specific additions.

Of course I will not be better in explaining the API and listing more details about it than the JEE tutorial from which I have already quoted most of what I mentioned above. You can know more about the API and how to use it in part III, Chapter 18 of the tutorial. I wish you all really find it useful.

Friday, November 23, 2007

SAVEPOINT Problem

Have you used the Database keyword "SAVEPOINT" before? Have you used it within Java?
First of all, I would like to give a brief definition and description for "SAVEPOINT".

"A savepoint is a way of implementing subtransactions (also known as nested transactions) within a relational database management system by indicating a point within a transaction that can be "rolled back to" without affecting any work done in the transaction before the savepoint was created. Multiple savepoints can exist within a single transaction. Savepoints are useful for implementing complex error recovery in database applications — if an error occurs in the midst of a multiple-statement transaction, the application may be able to recover from the error (by rolling back to a savepoint) without needing to abort the entire transaction.

A savepoint can be declared by issuing a SAVEPOINT name statement. All changes made after a savepoint has been declared can be undone by issuing a ROLLBACK TO SAVEPOINT name command. Issuing RELEASE SAVEPOINT name will cause the named savepoint to be discarded, but will not otherwise affect anything. Issuing the commands ROLLBACK or COMMIT will also discard any savepoints created since the start of the main transaction.

Savepoints are supported in some form or other in database systems like PostgreSQL, Oracle, Microsoft SQL Server, MySQL, DB2, and Firebird. Savepoints are also defined in the SQL standard."

This definition is quoted from wikipedia.


The first time I tried SAVEPOINT on Oracle 9i Database using JDK 1.4 - namely JDK 1.4.2_04 on JDevelope 10g- was about 2 years ago. At that time, I have been encountered with a problem when I tried to use it calling the method setSavePoint() in the java.sql.Connection interface. I also tried it, then, using JDK 5 but do not remember the exact version and faced the same problem. The problem was that I had the run time exception "java.lang.AbstractMethodError" and from the JDK documentation I understood that this can happen in run time only if a definition of some class has incompatibly changed since the currently executing method was last compiled.

I then have posted that issue on SUN forums, but unfortunately had no reply with a solution. You can find this post on the following link
Savepoint Issue
And this is a sample code similar to my own:
String s = "jdbc:oracle:thin:@" + strHostName + ":" + strPortNo + ":" + strDBName;
Class.forName(strDriverName);
Connection connection = DriverManager.getConnection(s,strUserName,strPassword);
connection.setAutoCommit(false);
.
.
.
Savepoint save =connection.setSavepoint();
.
.
.


Anyway, the only solution I have done was a little workaround. I just used the "SAVEPOINT" of Oracle Engine itself. All what I have done was something like the follwoing:
Class.forName(strDriverName);
Connection connection = DriverManager.getConnection(s,strUserName,strPassword);
connection.setAutoCommit(false);
.
.
.
Statement stmt = connection.createStatement();
for(int i=o; i< someArray.length ; i++)
{
.
.
stmt.execute("SAVEPOINT point"+i);
.
.
}

And then when I wanted to rollback to a specific savepoint I wrote code similar to

stmt.execute("ROLLBACK to point"+2);
This can rollback to the savepoint named "point2".


Cooool. It worked just fine for me.

To be frank, I have not tried to work with SAVEPOINT again lately, maybe because I did not encounter a business case that let me try it again. Also I have never tried it with JDK 6 or any other Oracle JDBC Driver, which I think was the main reason for the problem. But I am eager to know if anyone has recently worked with it, on what JDK version, and whether it has worked well from within the Java code and invocation for the setSavePoint() method of the java.sql.Connection interface and with what Oracle version and Oracle JDBC Driver version.

Waiting for your comments and experience conerning this matter.

Monday, November 19, 2007

Java Enhanced For Loops

Today, I am going to introduce one of the Java Technical Tips that I have previously received from sun on my e-mail. I wanted to share it with you . I hope every one who reads this tip will get benefit from.

The author of this tip is John Zukowski, president and principal consultant of JZ Ventures, Inc.
This tip was developed using Java SE 6.


Using Enhanced For-Loops with Your Classes

The enhanced for-loop is a popular feature introduced with the Java SE platform in version 5.0. Its simple structure allows one to simplify code by presenting for-loops that visit each element of an array/collection without explicitly expressing how one goes from element to element.

Because the old style of coding didn't become invalid with the new for-loop syntax, you don't have to use an enhanced for-loop when visiting each element of an array/collection. However, with the new style, one's code would typically change from something like the following:

for (int i=0; i
System.out.println("Element: " + array[i]);
}

to the newer form:

for (String element : array) {
System.out.println("Element: " + element);
}

Assuming "array" is defined to be an array of String objects, each element is assigned to the element variable as it loops through the array. These basics of the enhanced for-loop were covered in an earlier Tech Tip: The Enhanced For Loop, from May 5, 2005.

If you have a class called Colony which contains a group of Penguin objects, without doing anything extra to get the enhanced for-loop to work, one way you would loop through each penguin element would be to return an Iterator and iterate through the colony. Unfortunately, the enhanced for-loop does not work with Iterator , so the following won't even compile:


// Does not compile
import java.util.*;
public class BadColony {
static class Penguin {
String name;
Penguin(String name) {
this.name = name;
}
public String toString() {
return "Penguin{" + name + "}";
}
}

Set set = new HashSet();

public void addPenguin(Penguin p) {
set.add(p);
}

public Iterator getPenguins() {
return set.iterator();
}

public static void main(String args[]) {
Colony colony = new Colony();
Penguin opus = new Penguin("Opus");
Penguin chilly = new Penguin("Chilly Willy");
Penguin mumble = new Penguin("Mumble");
Penguin emperor = new Penguin("Emperor");
colony.addPenguin(opus);
colony.addPenguin(chilly);
colony.addPenguin(mumble);
colony.addPenguin(emperor);
Iterator it = colony.getPenguins();
// The bad line of code:
for (Penguin p : it) {
System.out.println(p);
}
}
}

You cannot just pass an Iterator into the enhanced for-loop. The 2nd line of the following will generate a compilation error:

Iterator it = colony.getPenguins();
for (Penguin p : it) {

The error:

BadColony.java:36: foreach not applicable to expression type
for (Penguin p : it) {
^
1 error

In order to be able to use your class with an enhanced for-loop, it does need an Iterator , but that Iterator must be provided via the Iterable interface:


public interface java.lang.Iterable {
public java.util.Iterator iterator();
}

Actually, to be more correct, you can use a generic T , allowing the enhanced for-loop to avoid casting, returning the designated generic type, instead of just a plain old Object .

public interface java.lang.Iterable {
public java.util.Iterator iterator();
}

It is this Iterable object which is then provided to the enhanced for-loop. By making the Colony class implement Iterable , and having its new iterator()Iterator that getPenguins() provides, you'll be able to loop through the penguins in the colony via an enhanced for-loop. method return the

By adding the proper implements clause:

public class Colony implements Iterable {


You then get your enhanced for
-loop for the colony:

for (Penguin p : colony) {

Here's the updated Colony class with the corrected code:

import java.util.*;

public class Colony implements Iterable {

static class Penguin {
String name;
Penguin(String name) {
this.name = name;
}
public String toString() {
return "Penguin{" + name + "}";
}
}

Set set = new HashSet();

public void addPenguin(Penguin p) {
set.add(p);
}

public Iterator getPenguins() {
return set.iterator();
}

public Iterator iterator() {
return getPenguins();
}

public static void main(String args[]) {
Colony colony = new Colony();
Penguin opus = new Penguin("Opus");
Penguin chilly = new Penguin("Chilly Willy");
Penguin mumble = new Penguin("Mumble");
Penguin emperor = new Penguin("Emperor");
colony.addPenguin(opus);
colony.addPenguin(chilly);
colony.addPenguin(mumble);
colony.addPenguin(emperor);
for (Penguin p : colony) {
System.out.println(p);
}
}
}

Running the code produces the
following output:

> java Colony

Penguin{Chilly Willy}
Penguin{Mumble}
Penguin{Opus}
Penguin{Emperor}

Keep in mind that the individual penguins are internally kept in

a Set type collection so the returned order doesn't necessarily match

the insertion order, which in this case it doesn't.

Remember to genericize the implements clause for the class

"implements Iterable " and not just say "implements Iterable ".

With the latter, the enhanced for-loop will only return an Object for

each element.

For more information on the enhanced for-loop, please see the

Java Programming Language guide from JDK 1.5.