[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Declaration and deployment of threads and thread pools i

[david.lloyd@jboss.com]

"alesj" wrote : ...And the MC part into deployers/deployers-impl.
  | (similar place where I put my -scanning.xml and -dependency.xml metadata)
  | 

Is this really the right place for adding a threads deployer?  All the deployers that "do stuff" seem to be in deployers-vfs (that's where all the other SchemaResolverDeployers are), but this doesn't really seem like the right place either since they're all related to J2EE deployment unit types for the most part.  This project might be the right place but maybe the threads deployer should be its own module?  I don't think it fits in in deployers-impl, unless that module is *intended* for such general-purpose deployers and there just doesn't happen to be any yet...

The most similar deployer to the ThreadsMetaData deployer I can think of is the ClassLoadingMetaData deployer, and that project lives completely separately.  This suggests to me that perhaps jboss-threads ought to be a separate project after all.

Also, What is there to gain by providing an interface-based view over metadata (like how it's done in org.jboss.deployers.spi.annotations)?  I haven't done this in my project - partially because I don't see the benefit, and partially because implementing BeanMetaDataFactory on the root metadata object might complicate things.  Am I missing out?


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201192#4201192

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201192