[jboss-dev-forums] [Design of POJO Server] - Using temp at undeploy

[alesj]

WRT:
 - https://jira.jboss.org/jira/browse/JBSEAM-3702

Moving Norman's post here:
"Norman Richards" wrote : 
  | Do you have a complete example of a jboss-structure.xml that works? Whenever I tried to create one, the only effect was that the application would be completely ignored and wouldn't deploy. Is it realistic to create a jboss-structure.xml that will work across multiple example apps with roughly the same structure? What about WAR files? I guess we would need two versions for each app - one for deploying as an EAR and for deploying as a WAR, right?
  | 
  | Is there any way we can add metadata to the jboss-app.xml to indicate how we want the app treated? It seems like this should be at most a one-line change for an app, if not the default behavior for the server. Deleting the file from the deploy directory has always been a clean way to undeploy an application, and it's really strange that now we don't have a clean undeploy. I'm not trying to be overly critical. I'm just trying to figure out what our official answer is to someone who asls "How do I undeploy an application?".
  | 
  | Before you could use the MBeans to deploy/undeploy an application. Undeploying did not remove the files from the deploy directory. In fact, you could easily use the MBeans to deploy/undeploy an application directly from your own project's build directory if you wanted. We generally didn't do that because making a connection to the MBeanServer required a login, which complicates things. But, it was definitely an option.
  | 

I'm thinking of some programmatic addition of this at structure recognition.
e.g. adding temp modification type to ContextInfo instance
I'll have a better look on Friday, but any suggestions/ideas welcome.


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

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