"alesj" wrote :
| But while we're trying to recognize the structure, to create a DeploymentContext
instance,
| we already potentially do some temp unpacking, ...
| That's why a need to do cleanup also on client side Deployment.
|
And even this is not enough.
As we might not even know how to cleanup all that we've temped.
e.g.
VFSDeployment only has an access to top root.
But if our deployment looks like this
* myapp.ear (exploded)
** mywep-ui.war (packed)
*** WEB-INF/lib
**** some-potential-persistence.jar
***** META-INF/persiostence.xml
In this case our WarStructure would temp that some-potential-persistence.jar
leaving us with no handle to clean it up.
This might work if Deployment had a knowledge of structure,
as we would be able to call cleanup on sub-deployment (the war),
but this again means it's messing with sever-side info.
Since it's only temps I wouldn't loose too much sleep over it
if there is no quick/non-dirty solution.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205510#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...