Hi Ilko,
For me, tracing the path through the following config files helped me learn alot about the way RAD and WAS work together:
- <RAD home>\runtimes\base_v7\profiles\<profile>\config\cells\<cell>\applications\<application>.ear\deployments\<application>\deployment.xml
- this file contains a property 'was.loose.config' which points to a 'looseconfig.xmi' file inside the .metadata of your RAD workspace
- this looseconfig.xmi contains a self explanatory description of your EAR in exploded form: every module or jar is represented by a tag which has a 'binariesPath' attribute.
- this binariesPath points to either a directory containing for instance the compiled classes or to a packaged jar or module.
The RAD servers view lets you select the deployment style (run with resources in workspace, etcetera) which influences the way in which the above setup is used: run with resources on server will obviously not make use of the looseconfig.xmi pointer to your workspace in the deployment.xml
The above describes the situation from a WAS point of view. M2Eclipse and RAD/EclipseWTP work together to create these configs from your pom.xml and the all important '.settings/org.eclipse.wst.common.component'
Marcel