Thanks for the reply, and sorry about taking the thread off topic
I'd moved the saaj apis up in the build path order already, but the problem was still there. I figured out it is the server that is the problem - so I put the apis in the server's classpath and got into all sorts of conflicts. I'll tackle that today.
I wonder if anyone knows the answer to this question:
Does SaaJ 1.2 support literal encoding of documents? At the moment my message gets encoded using soap's multiref array encoding, but I want it to send it literally using no soap encoding. If I manage to sort out the classpath problem above, does saaj 1.2 support literal encoding?
Any help much appreciated (and I've sort of brought it back on topic again now)