Skip to main content

Source code revision


summary: Fix for 11181
revision: 35586
author: tjquinn
date: 2010-02-10 17:33:04 UTC (5 years)
message: Fix for 11181

A problem occurs when all of the following is true:

- the app is an EAR which contains an app client
- the EAR is directory-deployed
- the EAR (say it's name is myApp) contains an app client module myAppClient.jar (which, because this is a directory deployment, is pre-expanded by the developer into myAppClient_jar)

Attempts to launch the app client fails with

java.lang.ClassNotFoundException: (main-class-for-the-client)

This is because the AppClientGroupFacadeGenerator placed the generated group facade into the app client's generated/xml directory whereas it should go into the EAR's generated/xml directory. As a result, the group facade would overwrite the JAR that is generated from the developer's expanded app client JAR directory. The first manifestation of this is the inability to find the main class from the client.

With this fix the group facade is placed into the EAR's generated/xml directory.

Approved: Abhijit
Tests: QL, deployment devtests; Elena's directory-deployed timersession app attached to the issue
Change Path Actions
M branches/3.0.1/appclient/server/core/src/main/java/org/glassfish/appclient/server/core/
Please Confirm