28 August 2009

OC4J Released

We published OC4J to OTN this week.

This is a maintenance release, but it has a sprinkling of new features that had been in the works for a while and have now made it into an official OC4J release.

Download location:


Updated Documentation:


Release Notes:


New Feature List:


I really like the small set of new features that have been added.

My pick of them, is probably the Peek utility. Peek provides a nice Web based front end for singing and dancing, all powerful, classloading functionality we've had in OC4J 10.1.3.x since its first dot zero release. Peek lets you drive easily around the classloading environment, visualizing the loader tree and letting you to drill down into it to see code-sources, packages, classes, etc. It also lets you execute the wide set of classloader queries we provide, directly from a Web browser. Really neat stuff.

There are also a set of new commands added to the admin_client utility, to support actions such as getting a listing of all deployed applications/web bindings, importing (and removing) shared libraries into applications, and a restart app command. Nice additions.

If you are still using OC4J and haven't yet moved over to the world of WebLogic Server, I reckon checking out OC4J would be worth your time.


Traveller said...

Hi Steve, I am working for a university project where we have this applcation running off on a 3-4 year old version of oc4j and jdk 1.4.2. I migrated it to oc4j and it worked like a charm.

However, I wanted to update java but as soon as I change it to jdk 1.5 or 1.6 I get the following error

oracle.oc4j.admin.internal.DeployerException: com.evermind.naming.SubContext cannot be cast to javax.sql.DataSource

I have posted this on the oc4j for over a week without any luck.

Any cluse as to why this is happening.

Thanks very much, Ken.

Buttso said...

Hi Ken -- can you send me the full stack trace from that error?

It looks like somewhere an object being retrieved from JNDi is trying to be being cast to a DataSource, but the actual object at the JNDI name isn't of that type.

Be interested to see what else is in the call frame.

You have my email address, so perhaps send it there.