What I'm trying to say here is that, the current ones (module factories) 
*doesnt* work ;)  It basically 100% ignore the component xml file or 
uses it 100% incorrectly. For example, the current esb module factory 
checks for one (ONLY ONE) wb-resource mapping tag. If it finds 2 
(because, perhaps, the user wants 2), the code simply ignores the second 
mapping, and takes the first.
  
    

Why ignore the component xml file means doesn't work, in practice, the
component.xml file
is impossible for users to edit it manually, you are expert ;-) , you
know about the virtual component
model, but most of users don't know and what it is for.
  

Then, rather than traversing that IVirtualFolder, the factory gets the 
underlying IContainer object, and just scans that folder... completely 
ignoring the point of using the virtual component model.
  
    

I have not investigated WTP code deep enough so I really don't find any
guides that told me
I must use Virtual Component to look for all related resources in module
factory, if you are familiar
with it, you can speak up or create a jira, rather than so easy to be
annoyed ;-) .
  

If we change it to use ComponentDeployable as module delegate, the old
component xml file doesn't
work, so we have think about support of old esb project.