IBM Support

Enhanced Enterprise Application (.ear) is not enabled while generating Java bean skeleton using top-down approach

Troubleshooting


Problem

This technote discusses a limitation in IBM Rational Application Developer for WebSphere Software v7.5.x, where the enhanced ear application is not enabled while generating Java bean skeleton using top-down approach, and provides a workaround to fix this issue.

Symptom

Consider the following two scenarios where Java bean skeleton is created from a .wsdl file (top-down approach) within Rational Application Developer for Websphere software v7.5.x:


    Scenario 1 (assuming the wsdl file is already existed within the workbench in a project) :
    1. Create a sample enterprise application ("Test1EAR") within the workbench including a web module ("Test1Web")
    2. Right-click on .wsdl file > Web Services > Generate Java bean skeleton
    3. Ensure in Java skeleton generation wizard to have the following settings: see image below
      • Set server as Websphere Application Server v7.0
      • Set Web Service runtime as IBM Websphere JAX-WS
      • Set Service project as Test1Web
      • Set Service EAR project as Test1EAR
      • Click Finish



When the process is finished, the generated codes are placed into Test1Web and if you right click on Test1EAR application > Java EE, you will see the following options as part of the available menu options: see image below
  1. Generate WebSphere bindings deployment descriptor
  2. Generate WebSphere extensions deployment descriptor
  3. Generate WebSphere programming model extensions deployment descriptor



Back to top



Scenario 2 (assuming the wsdl file is already existed within the workbench in a project) :
  1. Delete the .ear application Test1EAR and its web module Test1Web created in the first scenario

  2. Right-click on .wsdl file > Web Services > Generate Java bean skeleton

  3. Ensure in Java skeleton generation wizard to have the following settings: see image below
    • Name the .ear application as "Test1EAR" and name the .war module as Test1Web
    • Set server as Websphere Application Server v7.0
    • Set Web Service runtime as IBM Websphere JAX-WS
    • Type in Service project as Test1Web which will be created by wizard
    • Type in Service EAR project as Test1EAR which will be created by wizard
    • Click Finish



When the process is finished, the generated codes are placed into Test1Web and if you right click on Test1EAR application > Java EE, you will see the following options are "missing" in menu options:
  1. Generate WebSphere bindings deployment descriptor
  2. Generate WebSphere extensions deployment descriptor
  3. Generate WebSphere programming model extensions deployment descriptor

[{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Web Services Development","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.5;7.5.1;7.5.2;7.5.3;7.5.4;7.5.5;7.5.5.1","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
16 June 2018

UID

swg21446765

Page Feedback