At this point I feel after SCWCD one should go for SCBCD because of the reason that it follows a logical sequence and many study guides and mock exams are available. From some of the posts I read in the forum I got the feeling that one needs to be good in XML also for SCDJWS, so the way I am planning to tackle the SCDJWS is to first finish SCBCD then IBM XML Certification and then SCDJWS.
Originally posted by Bassam Zahid: Which one is more valuable or should I go for both ???
I'd vote for SCBCD first, then SCDJWS. I haven't taken either yet but judge for yourself. Take a look at SUN's page There are three objectives that mention EJB:
4.2 Given a set of requirements for a Web service, such as transactional needs, and security requirements, design and develop Web service applications that use servlet-based endpoints and EJB based endpoints.
8.3 Given a scenario, implement J2EE based web service web-tier and/or EJB-tier basic security mechanisms, such as mutual authentication, SSL, and access control.
9.1 Describe the steps required to configure, package, and deploy J2EE Web services and service clients, including a description of the packaging formats, such as .ear, .war, .jar, deployment descriptor settings, the associated Web services description file, RPC mapping files, and service reference elements used for EJB and servlet endpoints.
So knowing EJB could be helpful when web services are used in a J2EE context. However web services don't require EJB - for example Apache Axis only needs Tomcat. Also you should be able to acquire the SCBCD certification faster as some good guides are available. The first SCDJWS guide won't be available until earliest February 2006 and no one knows how good that guide will be. So working from Val's Specs-Objectives Mapping is the best option but it will be somewhat more time consuming. Also there is probably more EJB work than web service work, as web services are still evolving. If you are going to work with web services you'll probably be heavily supported by your vendor's tool. I'm not saying that the SCDJWS has no use - it just (at this point in time) doesn't seem to be as "useful" for developing web services as the SCBCD is "useful" for developing business components (within J2EE; as opposed to some other architecture/framework, e.g. Spring). The SCDJWS is probably more useful if you are working on the development of web services tools, rather than applications that utilize web services technology.