Orindasoft

FAQ: Questions

Installation

How do I install JDBCWizard on a non-windows operating system?
What are the differences between the Production version and the Demo version?
Which versions of Java do you support?
What database products can I use JDBCWizard against?
What are the differences between the Production version and the Demo version?
Why is my password stored in the PB2 configuration file?

Running

What happens when JDBCWizard reaches its expire date?
Why must I always provide a package name in Step 4.2?
Do you support Multi-byte character sets and datatypes?
Can I edit the PB2 configuration file?

Using the Code

Why are there so many methods for getting and setting numbers?
Which PL/SQL datatypes are supported?
Can we change the com.orindasoft.pub classes?

Public Library

How do we get the source code for com.orindasoft.pub?

Other Products

What's the difference between JDBCWizard and JPublisher?

Licencing

Who owns the generated software?


FAQ: Answers



Installation

How do I install JDBCWizard on a non-windows operating system?

Because JDBCWizard is written entirely in Java, it will run on any Sun Java platform. We test it using the Sun Java Virtual Machines for Windows and Solaris. For the convenience of the vast majority of our customers JDBCWizard is distributed as a Windows ".exe" install file. JDBCWizard can be installed on a non-Windows machine by first installing it on Windows and copying it to your target operating system. The default install includes Unix bourne shell scripts to run the application. If you absolutely can’t install it on windows first contact us using the Suggestions page and we will send you a zipped copy of an installation.

What are the differences between the Production version and the Demo version?

Which versions of Java do you support?

JDBCWizard generates code for the Sun Java Virtual Machine V1.2 and upwards. We do not test it with other vendors' versions of Java and are unable to offer support for Java implementations that are not approved by Sun. You can obtain Java here:

Get Java Button

What database products can I use JDBCWizard against?

JDBCWizard is designed to run against Oracle 8i, 9i and 10g and will not work with other database products. Rather than work on a generic solution for all databases, we decided to focus purely on Oracle.

What are the differences between the Production version and the Demo version?

Why is my password stored in the PB2 configuration file?

We store the password in an unencrypted form so that JDBCWizard can be run in non-interactive command line mode as part of a build process. Since most build processes hard code database user names and passwords this is not as big an issue as it looks at first. If you do not want a 'real' password in the file do the following:

  1. Disconnect from the database.
  2. Overwrite the contents of the Password field in the GUI.
  3. Save the PB2 configuration file.

You will now have a PB2 configuration file which does not have a valid password in it.



Running

What happens when JDBCWizard reaches its expire date?

The product will continue to run but will refuse to generate new code. Code generated by the full version of JDBCWizard has no expire date and will work indefinitely but you will have to maintain it by hand. Code generated by the Trial version stops running when the trial version expires.

Why must I always provide a package name in Step 4.2?

JDBCWizard will not generate code in a directory that already contains Java source that it did not generate. By insisting on a package name we make sure the user has picked a distinct location for generated code.

Do you support Multi-byte character sets and datatypes?

No, but we will do so in the future if there is sufficient customer interest. You may be able to generate most of the code you need by creating a 'single byte' version of your schema and running JDBCWizard against it.

Can I edit the PB2 configuration file?

The PB2 configuration file is a serialized Java Properties object. We strongly recommend that you use the GUI to maintain it. If you insist on changing it the manual contains a section titled "Editable Fields in the PB2 Configuration File" in the Appendix. The most common reason for editing the PB2 file is that you are running JDBCWizard on Windows but need to generate the output on a Unix system without invoking the GUI. In this case it is acceptable to change the value of CODE_BASE_DIRECTORY from a Windows path name to a Unix path name



Using the Code

Why are there so many methods for getting and setting numbers?

Oracle has its own internal format for storing numbers which has a range from 1E-130 to 10E125. PL/SQL provides a dozen or so numeric data types on top of this. It is often impossible to tell the actual Java data type should be used for a numeric parameter for a procedure because Oracle's NUMBER data type can plausibly be mapped to any numeric Java data type. Rather than have a user interface that would require you to specify the Java data type of every numeric parameter we opted to generate every possible access method.

In version 4.0.1709 we added the ability to 'turn off' numeric data types you don't want to use. This is documented in the Manual

Which PL/SQL datatypes are supported?

Which PL/SQL datatypes does JDBCWizard support?

Everything except the following:

In addition to 'normal' PL/SQL datatypes we support BOOLEAN, %ROWTYPE, %TYPE and Oracle TYPE. From V4.0.1892 JDBCWizard supports PL/SQL procedures that have VARRAYS and TABLEs as parameters. For a full list of supported Data Types, see the Documentation.

Can we change the com.orindasoft.pub classes?

You can change them but OrindaSoft does not support modified versions of the com.orindasoft.pub library. We recommend that you write your own classes that extend com.orindasoft.pub. The same principle applies to modifying generated code.



Public Library

How do we get the source code for com.orindasoft.pub?

The full version of JDBCWizard includes the source code for com.orindasoft.pub



Other Products

What's the difference between JDBCWizard and JPublisher?

We believe that JDBCWizard is a completely different and superior product to JPublisher because JPublisher has the following problems:

1. It requires you to make schema changes. You have to create Oracle TYPE objects for almost everything other than scaler variables. You then have to make sure that all your PL/SQL procedures use TYPE objects instead of %ROWTYPE or PL/SQL Package records. In many cases this involves rewriting large quantities of existing code.

2. Elaborate configuration files are used.

3. The generated code is almost unreadable.

4. It uses the SQLJ precompiler. SQLJ is like Pro*C - instead of writing .java classes you write and work with .sqlj classes, which are then processed into .java classes. This has changed slightly in 11g - According to the 11g JPublisher manual Oracle still creates .sqlj files. They then create .java files, after which they delete the .sqlj files. So you end up with Java but it's still via SQLJ.

In short: JPublisher does far less and is more complicated to use.



Licencing

Who owns the generated software?

You do. Orinda Software retains the copyright on the com.orindasoft.pub Library but you can continue to use it for as long as you want, along with any code you have generated.