Hi,
I have been using the plain java client to act as an interface onto RTC in a servlet. This works fine under WASCE (tomcat based), but when I try it under WAS it fails (known bug 76455).
The current process is something like:

JSP -> Servlet -> My SCM interface using plain Java client -> RTC

where the JSP and servlet are on WAS, and my SCM Interface using the PJC is a jar used by the servlet. RTC is standalone.

Seeing as this route of development has failed, can anyone suggest how else I can create my own servlet to:
1/ create project areas
2/ create streams
3/ check files in
4/ retrieve file content
5/ retrieve file version history

I'd be happy to learn and use the REST API, which would actually save having to use an intermediate interface, but as I understand it this doesn't cover SCM.

Currently I am having to run WAS and WASCE, using a proxy servlet on WAS. This will not wash for much longer... :-)

Cheers,
Crispin