FileStructure and FileMatcher

[adrian.brock]

A while ago we discussed adding FileMatcher "incallbacks" to the FileStructure
so we automatically added recognised file suffixes as subdeployments.

But this wasn't completed properly. Instead of making all
AbstractParsingDeployerWithOutputs (which knows about suffixes)
into FileMatcher implementations, only the bean shell deployer does this.

If we did this for every parsing deployer, then there would be no need for any hardwiring
in the FileStructure, e.g. -ds.xml and -service.xml

It would also correctly fail those deployments when the relevant parsing deployer
wasn't present. e.g. currently it will add -ds.xml as a subdeployment even
if the DataSource deployer isn't installed and then fail it with
"nobody processed the subdeployment" later on.

An additional request from Mark Newton is to apply the file matching process
to top level deployments as well.

Currently we allow a top level deployment to be called anything,
but that doesn't mean it will be correctly processed if the parsing deployer
doesn't recognise it.

The reasoning behind this was that I didn't want to have configure all
the suffixes in two places (the FileStructure and the ParsingDeployer),
but if the above change is implemented this argument goes away.

[adrian.brock]

A similar argument could be made for the jar suffixes in the JarStructure.
e.g. the SARdeployer could automatically add itself as a JARMatcher
accepting .sar extensions, etc.

Of course we should still hardwire .jar and .zip ;-)

In this case, it isn't as much of an issue of recognition since they are all jars
and the real test is whether something in META-INF/*.xml gets processed.

I say it is not an issue of recognition because everything can now be .jar
files, but there will be legacy deployments that use the old extensions
like .beans or .hibernate for subdeployments.

[alesj]

I can make this happen for CR1.
Integrating this with deployers tests that've already promised. ;-)

Can you create a JIRA issue?

[adrian.brock]

I've created two:

FileStructure: http://jira.jboss.com/jira/browse/JBMICROCONT-235
JarStructure: http://jira.jboss.com/jira/browse/JBMICROCONT-236

[alesj]

FileStructure: http://jira.jboss.com/jira/browse/JBMICROCONT-235

AbstractParsingDeployerWithOutput is not VFS aware.
I'll implement the FileMatcher in its direct subclass, AbstractVFSParsingDeployer.