> > >What are you talking about here? Why doesn't navigation of the >deployment information have any business in the deployment >structures? > This is EJB specific and requires the ApplicationMetaData and BeanMetaData classes, which then need other classes and such. I think that this could probably be cleaned up, but that will require much more work.
>What is the seperation that you are looking form? > I am seperating the core, which is everything that is setup and started from Server, minus the bits deployed from the current jboss-service.xml. DeploymentInfo is a core component to the core deployment framework (MainDeployer + SARDeployer) and it does not and should not know about plugin specific deployment bits. This helps keep the core simple and cleanly seperated from what are simply plugins... ejb is a plugin... so is the tm and so on. The only place where there was a problem seperating things was here and the simpilest thing todo was to move this code to the only place that was using it. Later we can figure out how to clean up this. My mail on DeploymentManager (or rather DeploymentFactory) and Deployment are aimed at just this... providing an interface for plugging into the core deployment system and allowing deployment specific methods (helpers as they may be) with out causing seperation problems. --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
