Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!

matt tee

Greenhorn
+ Follow
since Jun 25, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by matt tee

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)

Thanks,

Matt
Sorry to bump this thread but I am getting the same error. I have updated to SaaJ 1.2 (using the saaj jars from JWSDP 1.4) but it *still* comes up with an error message saying 'method not found - getSOAPHeader' when I try to run the servlet in websphere. I've added the jars to the build path of the project. I'm using websphere AD 5.1.

Any ideas why this is happening much appreciated. It's driving me mad. It's probably something really obvious as well...