[jboss-dev-forums] [Design of POJO Server] - Re: Stable deployment API for tools

[max.andersen@jboss.com]

Things that we do today on AS 4.x:

We "deploy" by copying files. We rely on both zipped and exploded deployments and even copies -ds.xml files for easy configuration.

Add an url for deployment location so we can avoid "polluting" the default/deploy directory

suspend/restart hotdeploy scanning to avoid unnecessary restarts while we are copying files
(even if we got an option for doing 100% remote deploy instead of file copy I still think file copy should be supported since it is the *simple* and works 99,9% of the time)


Things that would be really nice to do:

Do a remote deploy for remote systems and be able to somehow control where it gets "copied" or at least get info on where a deployment is located.

Get stacktrace/exceptions/logging per deployment so we can do a better error tracing than just tell them to look in the console. (this could be as simple as have a log file or folder per deployment instead of all munged together). Actual exceptions occurring doing runtime would help a lot too.






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

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