Basic JBAS-8357 solution deals with zipped archives. We also want to support exploded archives.

My thought is the scanner will inform the deployment repo of the new content. The repo instead of persisting a a1/b2c3xxxx/content file will persist a a1/b2c3xxxxx/url file that includes the URL of the exploded content in the hot deploy dir. When the repo is asked for the deployment, it will find the "url" file and use it to find the actual deployment content in the hot deploy dir. (It can actually keep this information in memory; the "url" file is to allow the connection to survive restart).