This is expected behavior. You can deploy the entire ear (with its nested children) by choosing to add / remove just the EAR. The childrern will follow automatically.
This is done this way in case you wanted to deploy a child war or jar stand-alone for some type of test or any other use case.
Basically, you configure what is a child of the EAR via module dependencies and other things... but that doesn't prevent you from deploying one of the children separately.
Hope this was clear.
- rob stryker
So first, why there's a difference between Jboss 4.2 server and the 'Jboss System Copy Server' projects layout?
Second, then I guess it is not working as expected,
I have created a new seam project through jboss tools packed as an EAR, so I got the following projects:
under myproject-ear->Properties->J2EE Module Dependencies I see myproject.war and myproject.ejb.jar with some other libs selected.
When publishing the project I see under server deploy folder a directory as: myproject-ear.ear as expected,
but under this folder I cannot find the other two sub projects folders (ejb/war) but only the content of the ear project.
which version are you using ? This was an issue in the old betas.
The System Copy Server is if you just want to deploy to some folder without regard to starting or stopping a server. It's meant to be a no-frills utility to just shove the jar'd project into a folder.
I know what is the System Copy Server for,
I'm using RC1,
btw, it is impossible to uninstall the tools from eclipse nor upgrade,
So I hope it's fixed in GA,
Anyway, according to this:
It seems like the upgrade is much easier with RHDS, so I'll buy it :-)