"dimitris@jboss.org" wrote:
The client only cares about deploying a URL. He doesn't care how this should be done or what is VFS and especially not what VFS options would be needed to workaround a particular problem.
"dimitris@jboss.org" wrote:
If we need to workaround the problem for this particular testcase, that's easy, just introduce a small delay and a note pointing to a JIRA with future work on this.
"dimitris@jboss.org" wrote:
Extending the MainDeployer api with implentation details doesn't offer any real value, it just complicates things.
"dimitris@jboss.org" wrote:
And BTW, I think all VFS options should be visible in bootstrap/vfs.xml with the user able to override them in the command line, or by modifying the file.
"scott.stark@jboss.org" wrote:
It should be the deployment that contains the metadata to setup the vfs behavior as needed, not the deployer call.
"alesj" wrote:"scott.stark@jboss.org" wrote:
It should be the deployment that contains the metadata to setup the vfs behavior as needed, not the deployer call.
Yes, this is probably the right fix.