Comments on: First Steps with Apache WSIF – Calling out to WSIF-alized SOAP WebServices and Java Classes

By: Clive Jefferies

Clive Jefferies — Fri, 16 Jan 2009 11:24:45 +0000

Here is a tutorial I wrote for anyone who is struggling to get their head round using wsif on Oracle:

http://soa-mobile.blogspot.com/2009/01/using-wsif-with-oracle-bpel-process.html

By: Antony Reynolds

Antony Reynolds — Fri, 03 Feb 2006 12:07:09 +0000

Great entry, nice clear example of using client side access.
Latest JDeveloper release now supports generation of WSIF binding for Java as well as SOAP 1.1 and 1.2.
As Sandor says, in Oracle BPEL the use-case is usually the other way round to this, as we use WSIF to invoke all interfaces, SOAP, Java or JCA – hence good to see another use for a very powerful level of indirection.

By: Sandor Nieuwenhuijs

Sandor Nieuwenhuijs — Fri, 27 Jan 2006 12:00:15 +0000

One remark about the use of WSIF in Oracle BPEL Process Manager: all Service calls
are done using WSIF, normally using the SOAP binding, and as soon as you use one
of the adapters (e.g. DB for PL/SQL, File, etc), we will use the JCA binding.
There are also two interesting blog entries from my colleague in the UK about WSIF
and BPEL:
http://www.orablogs.com/reynolds/archives/2005_09.html
and
http://www.orablogs.com/reynolds/archives/000747.html
There is also an interesting SOA Cookbook on this subject on OTN:
http://www.oracle.com/technology/pub/articles/bpel_cookbook/index.html
(see #4)

By: Aino Andriessen

Aino Andriessen — Wed, 25 Jan 2006 13:28:19 +0000

The above example requires a lot of libraries. Organizing them can be a tedious job, that can be made a lot easier with the use of Maven. This archive contains a Maven2 and JUnit enabled update of the example.

Unfortunately, some licences do not allow libraries to be part of the central Maven repositories. That’s, for example, the case for many javax libraries. So you’ll have to manually download and add activation.jar (v1.0.2), mail.jar (v1.3.2) and j2ee.jar (any version?!) to your local repository:
mvn install:install-file -Dfile=mail.jar -DgroupId=javax.mail -DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar
mvn install:install-file -Dfile=activation.jar -DgroupId=javax.activation -DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
mvn install:install-file -Dfile=j2ee.jar -DgroupId=javax.j2ee -DartifactId=j2ee -Dversion=1.4 -Dpackaging=jar

You can now run the untitests on the commandline with ‘mvn test’ or generate a project site with ‘mvn site’.

It is also very easy to generate Eclipse project files with ‘mvn eclipse:eclipse’, but make sure that you define in Eclipse the M2_REPOS variable that points to the maven repository root. Unfortunately maven cannot (yet?) generate the JDeveloper .jpr file, so I’ve included mine in the archive. Beware, it uses relative references to the files in my own maven repository, so you’d probably have to change these.