[jboss-dev-forums] [Design of JBoss Deployment Framework] - Re: Designing of jain-slee deployers for Jboss5.

[alesj]

"alexandrem" wrote : 
  | Hope so! It's a must-have feature, IMO. :)
  | 
 - https://jira.jboss.org/jira/browse/JBDEPLOY-135

"alexandrem" wrote : 
  | This looked like a good option... but we start at PARSE phase, and that seems like an issue, cause adding the jboss-dependency.xml didn't solved the problem.
  | 
Looks like you're doing too much in PARSE.
Like the stage name says, it should be just parsing. ;-)

That's why I put jboss-dependency.xml handling asap,
so it can add dependencies to as much as stages as possible.

You should split your deployment into more fine grained deployers per stages.

"alexandrem" wrote : 
  | One other thing I've noticed and would like some help on it, is the fact that the jars are not exploded anymore into a tmp folder, the reference to them now comes as, and using the above example, .../server/default/deploy/a.jar/a1.jar and  .../server/default/deploy/a.jar/a2.jar instead of the old way .../server/default/tmp/deploy/tmpXXXXXa.jar-contents/a1.jar. We used JarFile/JarEntry to handle it but now it fails due to those references not being a valid path for JarFile/JarEntry. I've managed a workaround for it, having a wrapper for the DeploymentUnit which will then enable me to return an InputStream to read the files... but not sure this is a good practice.
  | 
There is this discussion:
 - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146597

But if you ask me, 
you should just drop the old way (JarFile/Entry) and use VFS.

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

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