Skip to Content

In the previous installments of the WS-I Sample App Blog Series – An Introduction, my colleague Steve Winkler gave you some WS-I Sample App Blog Series – Background of WS-I, described the WS-I Sample App Blog Series – Overview of the Sample Application used for interoperability testing between different vendors and started with an WS-I Sample App Blog Series: Basic Design Decisions of SAP’s WS-I Sample Application implementation

My name is Martin Raepple, and I will now pick up the pen and dive deeper into the details of the implementation. I am also a member of the team that designed and implemented SAP’s new WS-I Sample Application. My primary focus is security, which will be the main topic of my next blog in this series. I my first installment, I want to share with you my experiences in Web Service Development with Java on the NetWeaver platform in the context of the WS-I Sample Application.


If you haven’t installed SAP’s new WS-I Sample Application yet, I would recommend doing so before you continue with this blog series. My colleague David Burdett posted a WS-I Sample App Blog Series: Download SAP “beta” Software that contains all the links and instructions how to download and install the software and documentation. You only need a running instance of SAP NetWeaver Web Application Server 2004s Java to deploy and test it. You can download a full Java Edition 2004s SP7 with a 90-day evaluation license from the SDN Download area.

Importing the Sample Application Source Code

This SDN download also includes SAP NetWeaver Developer Studio, SAP’s Eclipse-based Java IDE. In the Sample Application Download archive, you’ll find a folder with the name NWDSProjectSources, which includes the complete source code of the Sample Application. Please use the project import feature (File -> Import -> Multiple Existing Projects into Workspace) in NetWeaver Developer Studio to create the WS-I projects as illustrated below:


Most of the code excerpts referenced in the upcoming blogs are from the project After successful import of the project, I recommend to switch to the J2EE Development perspective in NetWeaver Developer Studio. From here it’s easy to navigate through the projects and code.

Roll up your sleeves

This installment starts with a short introduction to the code-first programming model used to develop Web Services in SAP NetWeaver 2004s and continues with a deep dive into the SOAP Extensions and customization of the Web Service Deployment Descriptor. It also provides a detailed description how to use custom SOAP headers in your applications.

Download the article

Reading and printing documents with a Web Browser that contain many illustrations and code excerpts does not always work perfectly. Therefore, I thought it is more convenient to provide the actual content as an article in PDF format to improve readability. So please continue to read the article here (PDF, 57k).

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Sidharth Deshpande
    Hello Martin,

    I have been following the sample app series and great to see some more docs regarding the same. I have imported the source code as has been suggested by you. However i am getting errors when i open the projects. First of all there are classpath errors. This i can resolve by adding appropriate jar files.

    The second type of error i am getting is “The Session Bean reference this web service is based on does not exist.” The resource is ws-deployment-descriptor.xml and the project is

    I am not able to resolve this. Can you please help me out with this. Also in J2EE DC perspective under ejb-jar.xml node i am not able to see any beans added nor is there an ejb-candidates node present.

    Please do let us your suggestions.


    1. Former Member Post author
      Hi Sidharth,

      thank you for downloading and testing the WS-I Sample Application. Please download an updated version of the source code / project export. This resolves the ws-deployment descriptor errors as well as the errors with the missing jar files. I added a new project to the archive which only contains the JAR files reqired by the other projects. I also fixed the classpath entries of the projects. They now point to the new project libs.

      Best regards


Leave a Reply