Oracle Java Bug Avoidance policy 1



It's absolutely unlucky to have a bug in the language of development as a compilation of people.

Because basically as grass-roots we, basically no solution, can only avoid!

?

Now take 2 examples to discuss with you:

1

Usage:

Used in Java

Runtime.getruntime (). EXEC ("Java-jar" + Strexepath + file.separator + "Tester_evsd/bin/api.jar type=2 command=1");

Run your own Write jar file

In the jar file, output log

This is a very simple procedure.

I'm going to get the following problem.

Phenomenon:

After eclipse begins execution, the jar can output a few logs from the beginning

But the back of the full output is not

Only eclipse terminates execution, and all logs are output

Avoid:

Do not execute jar directly, execute BAT file, OK

Thinking:

The wording should have no problem, can only be considered a Java problem, personally think this is a typical Oracle company's fault!!

?

2

Usage:

11g Database for Oracle

Client is available in version 11g

Phenomenon:

Application of ADO to ODBC data source in VB, program execution crashes on ODBC call to retrieve statement

Avoid:

With the 10g version of the client!

Thinking:

There should be no problem writing, the Oracle Company's program is not a typical test! , personally think this is typical of Oracle Company's fault!!

?

Unfortunately our position is too low, someone else Oracle will never see!

If you can see, want their program more test test!

?

Above

Oracle Java Bug Avoidance policy 1