Paul, As with all products that Oracle adopts (as their own), they originally start out as being the same, but slowly their paths diverge. OC4J is no exception. The first version of OC4J (220.127.116.11.1) was purely the "OrionServer" product, thinly disguised (instead of the "orion.jar" file, they named it "oc4j.jar"). The latest incarnation -- version 10.0.3 -- is very different to "OrionServer", since both "OrionServer" and OC4J have progressed several versions since the original OC4J, and, as I said before, the development paths of "OrionServer" and OC4J have completely diverged. Other examples of this behaviour include:
JDeveloper (originally JBuilder)
Oracle HTTP Server (originally Apache Web Server)
Good Luck, Avi.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com