Oracle Acquisitions... cannot remember all of them?

A friend of mine asked me some questions about Oracle and acquisitions. He could not, remember all of them and when they occurred... If you have the same questions take a look to the Oracle Acquisition page on Oracle.com since 2005:

• Oracle Strategic Acquisition

Some others are probably missing since in 2003/2004, Collaxa was acquired by Oracle. If you do not remember Collaxa was the first release of the BPEL Process Manager. You can also take a look to a part of the site that I like that is the Oracle's history.

Looking for a Wiki... take a look to WikiMatrix

You are looking for a Wiki... take a look to this very nice online tools:

• WikiMatrix

This tool can help you to find the best Wiki for you needs, free or not, hosted or not, ... and many other criteria. In addition to the Wiki Matrix, this site offers the same features for:

• Blogs
• Forums
• Podcatchers

Enjoy!

Oracle JAX-RPC: How to change the Character Encoding?

By default Oracle Web Service client is sending the SOAP messages using an UTF-8 encoding. This is the recommendation of WS-I Basic Profile. To be exact it says UTF-8 or UTF-16.

It is quite simple to change this encoding...
First you have to know that the JAX-RPC container will return the same character encoding than the one that is received. To change the character encoding, you just need to set the ClientConstants.CHARACTER_SET_ENCODING to the value you want to use. Here some simple client code:
Stub stub = (Stub)myPort.getPort();
stub._setProperty(oracle.webservices.ClientConstants.CHARACTER_SET_ENCODING, "UTF-16");

Most of the Web Services stacks are offering the same kind of utility to do that, for example here the property you must set to do the same in IBM's JAX-RPC implementation: com.ibm.wsspi.webservices.Constants.MESSAGE_CHARACTER_SET_ENCODING.