-
1. Re: Deployment Structure
starksm64 Sep 28, 2006 11:28 AM (in response to adrian.brock)I agree, but I don't think the current interaction between 1 and 2 is adequately defined. I believe I should be able to attribute the path /projects/web/test-web-app as a war in the vfs. This does provide a context for war related deployment analysis, but its neccessary.
Otherwise, I don't see how a structural deployer will be able to identify that /projects/web/test-web-app/test.jsp is a war with a single jsp file. -
2. Re: Deployment Structure
bill.burke Sep 28, 2006 12:11 PM (in response to adrian.brock)I have a possible problem with #3. Take EJBDeployer. I need to be able to identify whether the EJBContainer is deployed within an EAR as apposed to being deployed within a super JAR (jar that has other jars) or a SAR or some other non-scoping entity. I need this to be able to generate the kernel name of the EJBContainer (ear name + jar name) and default JNDI name.
I guess what I could just do is scope the name if the DeploymentUnit.getDeploymentContext().getParent() is not null. The deploy/ directory is not considered a DeploymentContext/Unit, right? -
3. Re: Deployment Structure
adrian.brock Sep 29, 2006 7:35 AM (in response to adrian.brock)"bill.burke@jboss.com" wrote:
I guess what I could just do is scope the name if the DeploymentUnit.getDeploymentContext().getParent() is not null. The deploy/ directory is not considered a DeploymentContext/Unit, right?
No, there should be apublic interface DeploymentUnit { ... DeploymentUnit getParent(); }
The getDeploymentContext() is only there so you can get on with
doing things while we work these details out.
It's upto you. You can either use the DeploymentContext,
and I'll fix it later, or you can change the DeploymentUnit now
if you think something is generically useful.