The certifications are only worth what you and others feel they're worth. I've found that my certifications instill at least some confidence in my abilities with given technologies, and they therefore serve the purpose of helping to convince others that I know what I'm talking about when I mention how easy or hard something will be to implement. So if you feel it's worthless, then don't take it.
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
SCDJWS 1.4 is targetted at J2EE 1.4. J2EE 1.4 supports JAX-RPC 1.1. JAX-WS 2.0 is supported by Java EE 5.0. So the question is whether one should be certified in a J2EE 1.4 supported APIs or wait for the rearchitected version's exam. It is same as what ppl ask for SCBCD 1.3 (still aligned to J2EE 1.3 version of EJB spec).
I think even though the architecture has changed for the WS stack in Java EE 5.0 so much so that they had to rename it from JAX-RPC to JAX-WS still most of what this exam covers will not be completely obsoleted by this change (i mean standards like SOAP 1.1, WSDL 1.1, UDDI v2 etc). And currently JAX-WS 2.0 is still in flux (they have a JAX-WS 2.0.1 too to support project Tango). Also you may get to work on JAX-RPC 1.1 even for new projects as the rate of adoption of a new J2EE spec/implementation is bound to be slow due to the costs/risks involved. So for the near future you are (imho) safe to take this version of exam now and upgrade later when the new exam (covering JAX-WS 2.0+) is available.
And if i remember right, Monson Haefel commented on JAX-WS (in one of his blog posts) as Sun trying to put lipstick on a pig, ie to say he was not very happy with the new architecture of WS stack too. [ September 25, 2006: Message edited by: Watsh Rajneesh ]