Download Java Game and Aplikasi Java for your phone

Posts Tagged ‘java’

There are a few things that make the SciPhone i68 so marketable. The first is the flow touch firmware that makes it more closely mimic the iPhone. The second is the inclusion of Java, which means that you can download and play literally thousands of third party software, applications, and games. It is for this reason that the SciPhone is a really nice phone for gamers. Still, I occasionally get emails asking me if you are stuck with the preloaded gaming options. You definitely are not. But, you’ll need to know how to get the games on to your phone, which I’ll explain in the following article.

Where To Get Cool Games For The SciPhone I68: As I alluded to earlier, Java is where it is at. The earliest clones did not have this feature. If you google or search “get jar” into any major search engine, you’ll see sites where you can download Java games for free.

On the top of the main page, click on “software.” Then, on the left hand side of the site (toward the bottom) is a games icon. If you click it, you’ll be given the most popular downloads first. But if you have an idea as to what type of game you want, they have it broken down into genres like action, adventure, sports, etc, which can make things easier and quicker.

Once you find the game or games you want to download, click on it. Most games will just give you the jar files in the download box. Some will ask for your device though. In this case, you’ll enter the only CECT option, which is the A100 (works on all models.) Sometimes, this option isn’t given (rarely). In this case, many of the Nokia options will work, particularly the 2610.

Downloading Java Games On Your SciPhone I68 JAVA : Once you’re at this step, you’ll need to get the game onto your phone. You can do this in two ways – via your PC or through the phone’s web browser. (Obviously, you’ll have to have your WAP browser set up properly for your carrier.) Note that opera mini usually will not allow downloads, so you’ll have to use the WAP browser. But, the game will give you the exact link or code so that you can easily get to it from the “go to” icon on the browser. Once you type in the html address and code, you’ll simply hit “download.”

Alternatively, you can download the game via USB port. This is how I prefer to do it because it saves me data time and money and also, I like to have a copy on my computer in case it should accidentally be deleted. For this, hook the USB up to both your computer and phone. Hit “mass storage” on the phone. Then hit the jar file / game you want and scroll to “save as.” Then, find your device in the “save in” folder . This will usually be the bottom option. (For me, it’s often the K drive.) Once you’ve chosen this, hit save.

Then, unplug the phone from the USB. Go into the documents icon of the phone. Go into “memory card.” Go into “received.” (If you don’t have a received file, go into whatever file you saved the jar game into.) You will see the name of the game listed. Click it. You will be given a list of options. The first is “install.” Click install. The phone will install the game and you are almost done.

The final step is to play the game. For this hit your Java icon. Then click “installed java software.” At the bottom of the list, you’ll see your game listed. Click it and then hit launch. That’s really it. (The process for getting to and playing the game is the same no matter how you installed it.)

Incidentally, the same process goes for any Java download including software, productivity, and browsers like Opera Mini, etc.

The word Java has taken on several meanings in comtemporary culture. In the computer world, it is a particular computer programming language that creates eye-catching applications used mostly on websites. In restaurants and bars, the word is often used interchangably with coffee. The real Java on the other hand, is the most populous island in Indonesia, where the capital Jakarta is located.

Java island is mountainous with numerous active volcanoes. The climate is muggy year-round, often punctuated by monsoon rains. Along with the fertile soil that surround the volcanic areas, the early Dutch settlers found these conditions to be very conducive to growing coffee.

Arabica was introduced to Indonesia in the 17th century and this was planted vigorously by the Dutch colonial government. The Arabica was eventually wiped out for the most part by a plague known as coffee rust although coffee plants in other regions were not affected. Robusta was the logical alternative because of its resistance to diseases.

Later on in the early 20th century, the colonial government would build the infrastructure to confine the growth of coffee to East and Central Java. East Java would produce Arabica simply because of their more mountainous regions while Central Java primarily produced Robusta.

Today Indonesia is the biggest producer of coffee in Southeast Asia and third in the world. The coffees they export are from both the Arabica and Robusta stocks although gourmet coffee makes up only about ten percent of their export. This is due mainly to the roles that the plague along with World War II and internal political strife have played in forming the Indonesian coffee industry.

Arabica from Indonesia are primarily from the islands of Java, Sumatra and Sulawesi. Sumatra is also mountainous with active volcanoes. The highlands to the north and west of Sumatra produces very high quality Arabica beans. Sulawesi coffee is similar in character and appearance to the Sumatran.

Even though Java is the most well-known of Indonesian coffee exports, many experts agree that Sumatra coffee is the best of the lot owing to a fruity and syrupy taste. It is unclear why coffee drinkers today have equated the word java with coffee itself. One story tells us that because coffee from Java was so popular at the time, merchants would brand their coffee with that name in order to capitalize on its popularity as well as increase sales. As you can see, brand marketing was very much alive in the 18th century.

And because brand marketing is often mischievous and creates a lot of unnecessary hype. As a result, buying a bag of coffee can suddenly be confusing especially when the word “Java” is present in the packaging. Are you actually buying coffee of the gourmet variety from the island of Java or just some plain coffee using the term just to make it a more attractive, not to mention expensive, commodity? Adding to the mess, when looking up the word itself on the search engines can take you to pages of undecipherable computer programming language when all you wanted was a hot cup.

That being said, when looking specifically for Indonesian coffee, the most common is Java Estate. But if you want a treat, look beyond Java and let your taste buds feast on Sumatra Mandehling instead. It is sure to erase any confusion.

SCJP 5.0 – Carving a well qualified Java Tiger Programmer

Sun Microsystems offers many certifications starting from programmer level to architect level. The latest version of programmer (SCJP) exam is SCJP 5.0 – Sun Certified Programmer for the Java 2 Platform, Standard Edition 5.0 (CX-310-055). Sun started calling SCJP 5.0 instead SCJP 1.5 from this new version.

Achieving this certification provides clear evidence that a programmer understands the basic syntax and structure of the Java programming language based on new syntax introduced in SCJP 5.0. The certified programmer can create Java technology applications that run on server and desktop systems using J2SE 5.0 ( Java Tiger). Java Tiger is the another name of J2SE 5.0.

NOTE: The external version number of this release is 5.0 and its internal version number is 1.5.0.

What is new in Java Tiger ?

Changes include generic types, metadata, autoboxing, an enhanced for loop, enumerated types, static import, C style formatted input/output, variable arguments, concurrency utilities, and simpler RMI interface generation.

Wow ! Thanks to Sun Microsystems for providing such a valuable features for Java Programmers.

So, if you decided to take Sun Java Programmer certification (SCJP) go ahead with SCJP 5.0 and be a Java Tiger Certified Programmer and enjoy the benefits of new features.

Changes in Exam Objectives from SCJP 1.4 to SCJP 5.0

SCJP 1.4

SCJP 5.0

Section 1: Declarations and Access Control

Section 2: Flow control, Assertions, and Exception Handling

Section 3: Garbage Collection

Section 4: Language Fundamentals

Section 5: Operators and Assignments

Section 6: Overloading, Overriding, Runtime Type and Object Orientation

Section 7: Threads

Section 8: Fundamental Classes in the java.lang Package

Section 9: The Collections Framework

Section 1: Declarations, Initialization and Scoping

Section 2: Flow Control

Section 3: API Contents

Section 4: Concurrency

Section 5: OO Concepts

Section 6: Collections / Generics

Section 7: Fundamentals

Is SCJP 5.0 easy compared to SCJP 1.4 as it has limited number of sections? No, most of the concepts are new in SCJP 5.0. Some of them are not related with SCJP 1.4.

SCJP 5.0 Exam Details

Delivered at: Authorized Worldwide Prometric Testing Centers

Prerequisites: None

Other exams/assignments required for this certification: None

Exam type: Multiple choice and drag and drop

Number of questions: 72

Pass score: 59% (43 of 72 questions)

Time limit: 175 minutes

After completion of SCJP 5.0 exam you are familiar with Java Tiger concepts like generic types, metadata, auto boxing, an enhanced for loop, enumerated types, static import, variable arguments, etc.

How long I need to prepare for this exam?

The answer is it depends on your current knowledge in Java programming and OO Concepts. You may get an approximate estimation from EPractize Labs SCJP 5.0 Preparation Time Calculator.

How to start? Where to start?

First go to Sun’s website and understand the exam objectives. http://www.sun.com/training/catalog/courses/CX-310-055.xml

Plan for your preparation. If needed calculate an estimation from EPractize Labs SCJP 5.0 Preparation Time Calculator.

Identify your weak areas based on the exam objectives. Set more focus on those topics.

Study and workout the program examples.

Practice with mock exams and see where you are. Continue your practice till you achieve your goal.

Achieve your SCJP 5.0 certificate and share your success WITH YOUR FRIENDS AND COLLEAGUES!

Recommended SCJP 5.0 Exam Preparation Kit

Use SCJP 5.0 Exam EPractize Labs – Personal Edition for empowering your preparation by PPA-1(Plan, Practize, Achieve) methodology.

SCJP 5.0 Certification Benefits

For the Individual

Clear evidence that you are a Java Tiger programmer.

The certification empowers in driving Java Programming based on J2SE 5.0.

SCJP 5.0 certified programmers can easily design and develop the code based on J2SE 5.0.

Being a SCJP 5.0 certified programmer helps you to improve your career potential, gain more respect, boost up your job security and opportunities.

With SCJP 5.0 certified programmer, you become more competitive in the job market.

For the organization

Enables management to distinguish SCJP 5.0 certified programmer as Java professionals who can develop quality code efficiently and effectively.

Helps in deciding the best development APIs or Java Components based on latest J2SE APIs.

More confidence to work on Java Code technical decisions with business partners.

Enables project team to get best coding practices and guidance from a qualified Java Programmer.

Good Luck !

If you’re like me, you spend a lot of time dealing with legacy code that, for whatever reason, does not take advantage of modern methodologies and libraries. I’ve taken over Java projects that contain hundreds of thousands of lines of code and not a single third-party jar other than a JDBC driver! One of the most common examples of this is the implementation of the data access layer. These days, the de facto methodology involves Hibernate and DAOs, usually managed by Spring.
This article will detail the steps I recently took to covert a large application from custom-written data access to Hibernate and Spring using the refactoring facilities in Eclipse. The key with this refactorization is to get the existing business logic code (Struts Actions, JSPs, Delegate classes, Business Service classes, etc.) to access the datastore using Hibernate, managed by Spring, without manually changing any of that code directly. Part 1 will include creating the Hibernate data object classes, DAOs, and refactoring the existing code to work with these newly created types. Part 2 will conclude the project with integration of the Hibernate DAOs and wiring everything up with Spring.
First of all, we need to create our Hibernate model and DAO classes. Obviously, since we’re dealing with a legacy application and data structure, we will want to use a bottom-up approach to building our data access layer. This just means that we’re going to generate the Java code and appropriate Hibernate config files from the existing database. There are many tools freely available to make this process very painless. I recommend an Eclipse Plugin for creating and maintaining the Hibernate artifacts (Google “Hibernate Eclipse Plugin” to get started). The structure and requirements for creating Hibernate classes and config files are well documented elsewhere, so I won’t go into detail here. However, in this particular project, the Hibernate DAO lifecycles are managed by Spring, so the DAO classes should all extend HibernateDAOSupport.
Now we have java classes (POJOs) which map to our database tables, but none of the existing code uses these new data object classes. This is where the refactoring tools of Eclipse comes in really handy. For example, say we have a legacy class called AccountInfo which corresponds to the ACCOUNT database table. Right-click the class and select Refactor -> Extract Interface. On the dialogue box, call the new interface IAccount and make sure you select “Use the extracted interface type where possible.” Choose the other options according to your preferences. Click OK and kick back while Eclipse changes every occurence of AccountInfo references to IAccount references and recompiles. Of course, do this with each object model class.
If you never realized why OOP languages are so great, you’re about to. Now we’re going to refactor the code so that all of the existing legacy can be hooked into the new Hibernate model classes instead of the legacy ones. Continuing with the AccountInfo example, create a new class – you’ll probably want to create a new package for this step – called Account that extends the Hibernate POJO for Account and implements the new IAccount interface.
This next part is the most time-consuming, but really isn’t that bad. At this point, the newly created class will probably contain a bunch of empty methods containing only TODO comments. This is because the IAccount interface most likely defies a bunch of methods that are not implemented in the Hibernate Account POJO. To deal with these, we basically want the new Account class to delegate to its generated superclass whenever necessary to satisfy its contract as an IAccount type. As a real world example from the application I was working on, the legacy AccountInfo class defined a getter/setter pair for a property called username, whereas the corresponding column in the ACCOUNT table was actually LOGIN_NAME. To deal with this, you would simply implement the get/setUsername methods in Account to delegate to get/setLoginName (from its superclass). I also had to translate between various data types quite a bit. For example, the legacy code would define many properties as Strings even though the corresponding piece of data in the database was defined as an INT or TIMESTAMP. Again, do this with each object model class.
To finish up the data model layer, edit the appropriate Hibernate and Spring configuration files to refer to these new object model classes. The application now has the ability to map database records to Java objects via Hibernate, and the legacy code which refers to these classes has not required any editing by hand. To finish up this refactorization project, we need to hook in the Spring-supported Hibernate DAOs in a similar way. In Part 2 of this article, I will discuss refactoring the legacy code to read, write, and update data using Hibernate and Spring.