Hi,
Unless I'm mistaken, there're 4 planners: Service, Jetty, Connector and EJBModule. Their names are selfexplanatory as to what they can plan to deploy. The missing piece is a EAR deployer. Once a scanner (FSS or WDS) finds a META-INF/MANIFEST.MF it adds the resource which contains the manifest to a list of resources to be deployed. As none of the planners are willing to take over planning of EAR deployment (as they're looking for other files in META-INF as indication of its correctness), the only way to deploy that EAR is to remove its META-INF directory.
I've been thinking about how to achieve EAR deployment and what the planner could do. The main thing the planner must do would be to plan to create a class-space for the EAR and then ask other planners for deployment of the rest and tell them what classspace it should belong to. I think other EJBs/WARs/RARs that are not part of EAR should belong to DEFAULT EAR. It would then become a reserved name, so no DEFAULT.ear may get deployed.
I think I'm ready to tackle the issue and prepare something in the coming days. Before I do it, though, I'd like to find out if it's already being worked out. Also, your comments/recomendation are highly appreciated as while I'm reading the message I don't see any problems to sort it out very easily (I know, the devil is in details).
BTW: What is org.apache.geronimo.kernel.deployment.ApplicationDeployer for? Would it be of help somehow?
We could also talk it over on IRC tonight.
Jacek
