Jean-Sebastien Delfino wrote:
[snip]
ant elder wrote:
Cool, that works and gets me the name thanks.
Should Component have a URI? The o.a.t.assembly.Component interface
doesn't
have a get/setURI which seems to match the schema in the spec, but
page 53
line 2362 of the Assembly spec makes it sound like it should.
...ant
Line 2362 says: The component URI above is for a component that is
deployed in the SCA Domain. The URI of a component defaults to the
name of the component.
I'm assuming that this talks about components declared in deployable
(top-level) composites which are included in the SCA domain and that
this URI would not apply to components declared in nested composites.
This is the only place in the whole spec that mentions this so before
adding a URI to all components I'd like to double check with the spec
folks that it's not a bug in the spec :)
The good news is that the second sentence allows the default URI to be
the component name, which we already have in the model :)
Ant,
I asked the spec assembly workgroup. Lines 2362-2367 of assembly spec
are not correct. They added the following text to the errata at
http://www.osoa.org/display/Main/Errata+for+Assembly+Model+V1.00:
7. Component URI is not well described
Lines 2362-2367 talk about Component URI for components deployed
directly into the SCA Domain. The text in these lines implies that
there is a settable component URI attribute. However, there is no
Component URI attribute described in the specification or in the XSDs.
This needs to be corrected.
I suggest to wait for the correction to start implementing this URI, as
I'm not sure if a URI attribute is going to be added to Component or if
URI is going to be removed, and for now use the component name.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
