"alesj" wrote :
| Yes, it should be the structure deployer to handle this, not policy creation code.
|
In this case it could also be some real deployer (pre CL stage),
similar to what we do in InMemoryClassesDeployer.
But since you're already parsing manifest for symbolic name in structure deployer,
I guess you don't gain that much by moving this code on top of existing OSGiMetaData
in some real deployer.
e.g. it would make sense to move it to real deployer and work on existing OSGiMetaData,
hence not reading manifest headers twice
But like I said, this is not the case here, as you *must* already read it in structure
deployer
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259312#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...