Whats the difference between OrindaBuild and JPublisher?
We believe that OrindaBuild 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 co
