PQ58388: J2EE APPLICATION CLIENT TOOL CAN'T RUN AGAINST "LOOSE" MODULES | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Want to take advantage of the WebSphere Client Application Tool runtime in the WSAD environment in order to unit test J2EE clients. Currently when working outside WSAD in a file-system equivalent structure and using the WAS LaucnhClient tool that: 1. Able to structure an EAR module as directory with files in which EJB and Client modules, also as directories and files, as subdirectories to the EAR module directory. This works fine. 2. If, however, the EAR module is at the same directory level as the EJB and Client modules, which is exactly how it is structured in WSAD as projects, it does not work and it appears the problem might be that the absolute path attribute which works for the server runtime so that the files can be loose like this, might not be set up to work like that in the WebSphere Application Client tool. . Routinely get the following exception: . E:\javawork>LaunchClient HelloWorld IBM WebSphere Application Server, Release 4.0 J2EE Application Client Tool, Version 1.0 Copyright IBM Corp., 1997-2001 WSCL0012I: Processing command line arguments. WSCL0013I: Initializing the J2EE Application Client Environment. WSCL0100E: Exception received: com.ibm.etools.archive.exception. OpenFailureException: Internal Error at com.ibm.ws.client.applicationclient. ApplicationClientMetaData.getURIForMOFFile (ApplicationClientMetaData.java:583) at com.ibm.ws.client.applicationclient. ApplicationClientMetaData.<init>(ApplicationClientMetaData. java:377) at com.ibm.ws.client.applicationclient.ClientContainer.<init> (ClientContainer.java:111) at com.ibm.websphere.client.applicationclient.launchClient. createContainerAndLaunchApp(launchClient.java:433) at com.ibm.websphere.client.applicationclient.launchClient. main(launchClient.java:304) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158) Defect 116966Local fix Problem summary **************************************************************** * USERS AFFECTED: Webphere Application Server users who have * * completely expanded Enterprise Archive * * files and who are running J2EE Application * * Clients. Also, users of WebSphere Studio * * Application Developer who are unit testing * * J2EE Application Clients. * **************************************************************** * PROBLEM DESCRIPTION: Internal Error Exception when running * * the launchClient command or unit * * testing J2EE Application Clients using * * WebSphere Studio Application Developer. * **************************************************************** * RECOMMENDATION: * **************************************************************** The problem is caused by the WebSphere J2EE Application Client code not correctly handling Enterprise Archives that are completetly expanded.Problem conclusion The Websphere J2EE Application Client code was changed to correctly handle fully expanded Enterprise Archive files.Temporary fix An eFix is available.Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ58388
IBM Group: Software Group
Modified date: Mar 7, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.