|summary:||Additional fix for 10947|
|date:||2009-11-17 21:26:54 UTC (5 years)|
|message:||Additional fix for 10947
These changes augment earlier changes for this issue, discovered as a result of further testing:
1. FacadeLaunchable - Annotation processing for managed bean support is suppressed during Java Web Start app client launches. (The anno processing logic uses File objects; Java Web Start does not make the downloaded JARs visible as files. We'll look at generalizing the anno processing to include this case in v3.1 or later.)
2. AppClientDeployerHelper - During directory deployments the URI to the submodule might be the URI to the developer-provided expanded directory for that submodule. Classically, for a submodule myEJB.jar the expansion directory would be myEJB_jar. But the developer could have created a directory named myEJB.jar instead. The app client deployer logic that deals with directory deployments did not adequately account for that case.
3. NestedAppClientDeployerHelper - The earlier check-in did not correctly include a JarArtifact in the files to be downloaded.
4. AppClientHTTPAdapter - The changes correct the handling of the special-purpose (undocumented) accarg query string parameters during Java Web Start launches.
Tests: QL, deployment and ejb and selected webservices devtests; Java Web Start tests
Check-in approved by Jerome