PK41926: ERROR "UNABLE TO PARSE CONFIG FILE" WHEN USING COMMAND WSDL2CLIE NT WITH THE OPTION WSSECDIR

APAR status

• Closed as program error.

Error description

• Environment:
  - OS (name, language, version or SP): Microsoft Windows XP SP2
   - Product name (Build ID or version/patch level): IBM Rational
  Application Developer 6.0.1.1 iFix004
  Reproducible Y/N: Y
  
  Description of problem:
  When trying to use the WSDL2Client command with the option
  wsSecDir to generate Web Services with WS-security configured,
  the error "Unable to parse config file" is raised
  
  Steps to reproduce:
  1) create a WS project in RAD and configure the ws client
  binding and extension to use LTPA token.
  2) copy the wsdl files into another directory
  (c:\temp\TestWSClient).
  3) copy the ibm-webservicesclient-*.xmi under
  c:\temp\TestWSClient\conf\ltpa
  3) run the command
  E:\Programs\IBM\Rational\SDP\6.0\bin\WSDL2Client.bat -project
  c:\temp\TestWSClient -clientType servlet -genMain TestServlet
  -wsSecDir c:\temp\TestWSClient\conf\ltpa -verbose
  C:\temp\TestWSClient\TestWS.wsdl
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the Rational Application        *
  *                 Developer command-line WSDL2Client script    *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using the WSDL2Client script       *
  *                      with the -wsSecDir option then an       *
  *                      'Unable to parse config file' error     *
  *                      occurs.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using the WSDL2Client script with the -wsSecDir option an
  'Unable to parse config file' error occurs.  This error is
  caused because the tool is attempting to locate the deployment
  descriptors to copy in the projects META-INF directory rather
  than WEB-INF for web clients.
  

Problem conclusion

• The WSDL2Client script will now properly look in the WEB-INF
  directory for the deployment descriptors when using the
  -wsSecDir command-line option.  The fix for this APAR is
  currently targeted for inclusion in Rational Application
  Developer v6.0.1.2.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBAPP SERVER A

• Fixed component ID

  5724J0820

Applicable component levels

• R600 PSY

     UP