Would we also need to post process the contribution to check for unresolved references ? I'm guessing that, file references outside from the contribution scope will always be on the unresolved status ,and would need further processing.
On 5/29/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Venkata Krishnan wrote: > Hi, > > The property value definition for a component can have an attribute named > 'file' that points to a xml file that might contain the value for a > property. The question is - now that the contribution service is in shape > must it be used to resolve this file as well just like all other > artifacts. > If so could somebody please provide some pointers on how to do this. > Thanks > > - Venkat > I think it would be a good idea to use it, this would require a simple change to our ArtifactResolver implementation to support something like a FileReference object, similar to what we've done for classes with ClassReference, but we probably also need to confirm what the SCA assembly spec actually means by: <<< 287 - file (optional) – a dereferencable URI to a file containing a value for the property >>> In particular: - foo/bar.xml - is foo/bar.xml relative to the current SCA contribution? or the referencing composite file? - /foo/bar.xml - is /foo/bar relative to my hard drive? or the current SCA contribution? - http://foo.org/bar - is this allowed? -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
