Nasty defect in WAS 7 - Websphere

This is a discussion on Nasty defect in WAS 7 - Websphere ; When a session EJB acts as a web service, system fails to locate the client side WSDL file. It works fine in RAD7.5 development environment. Problem happens when you deploy the EAR file to the server. Exception is: Caused by: ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Nasty defect in WAS 7

  1. Nasty defect in WAS 7

    When a session EJB acts as a web service, system fails to locate the client side WSDL file. It works fine in RAD7.5 development environment. Problem happens when you deploy the EAR file to the server. Exception is:

    Caused by: java.io.FileNotFoundException: .\META-INF\wsdl\HelloService.wsdl (The system cannot find the path specified.)
    at java.io.FileInputStream.open(Native Method)

    It seems that, the client runtime is trying to open the WSDL file from the file system. This will fail because the file happens to be inside the EJB JAR file. It works fine when run from RAD because the EJB module is in exploded form with all files accessible from the file system.

    Please see attached EAR files. EJBModuleB in AppB is a client of EJBModuleA in AppA. To test:

    1. Install the EAR files.
    2. Start the apps.
    3. From a browser enter: http://localhost:9080/WebModuleB/index.jsp

    Is there no way to call a web service from an EJB?

  2. Re: Nasty defect in WAS 7

    Correction. First sentence should read "When a session EJB acts as a web service *client*, system fails to locate the client side WSDL file"

+ Reply to Thread