Venkat,
Sebastien is correct, the spec has a hole here, so let's try to
fill in the hole to see what works, and then feed it back to
the spec community. I would have opted for "relative to the
contribution". If the URI is absolute, then it should be treated
as absolute. IMHO, this is not very useful, but maybe someone
can come up with a use case for it.
This gives the developer the freedom to name and package
the XML file anywhere they want so that it can be referenced
from multiple component definitions in the contribution.
Other opinions?
Dave
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, May 29, 2007 6:45 PM
Subject: Re: Component Property Definition - resolving 'file' attribute
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
