Yes, I meant we should tidy up the processors to tolerate the wrong content
and return null. An extreme example is that we have
CompositeDocumentProcessor registered against the .composite file and it
will fail if a .composite file happens to be a non-SCA artifact.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Friday, March 27, 2009 4:58 AM
To: <[email protected]>
Subject: Re: [1.x] Jar artifact processing
snip...
In the current code, we register the URLArtifactProcessor against the
artifacts based on the names of the artifact URI/URL. In 1.x, the
artifact
type is either a file extension or file name and the processors are keyed
by
the artifact type. As a result, only one processor will be picked. In
2.x, I
add the wildcard support which allows more than one processors to match
the
same artifact (I probably have to allow more than one processors to be
invoked). Meanwhile, the URLArtifactProcessor should be implemented to
tolerate the artifacts whose content cannot be processed. In such cases,
null should be returned and the next matching processor can deal with it.
By "meanwhile" here Raymond do you mean these are the extra things to
do ontop of the other 2,x changes you've made. In 1.x we don't have
the wildcard support just yet.
Simon