[
https://issues.apache.org/jira/browse/TUSCANY-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604572#action_12604572
]
Raymond Feng commented on TUSCANY-2383:
---------------------------------------
If the component is implemented in java, I think this is a grey area in the
spec. The spec says the configuration in the componentType should be compatible
with the result from the instrospection of implemention. Let's say your purpose
is to declare a property in the componentType file, then it has to be
associated to a field or setter in the java class. Is the field/setter required
to be protected or public? My understanding is that we can use the
componentType to provide a default value to a property, but not "add" a new
property if it doesn't exist in the impl class.
There are discussions on the ML about if we should use componentType to
redefine the service interface using interface.wsdl. I think these are in the
same area.
> Cannot define component property with Component Type File
> ---------------------------------------------------------
>
> Key: TUSCANY-2383
> URL: https://issues.apache.org/jira/browse/TUSCANY-2383
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-Next
> Reporter: Kevin Williams
>
> Lines 450-451 of the Assembly spec:
> The componentType element can contain Service elements, Reference elements
> and Property elements.
> I defined a test that inspects an injected property value. In the initial
> version I defined the property using the @Property annotation. I then tried
> replacing the annotation with an entry in a Component Type File without
> success.
> The test:
> org.apache.tuscany.sca.vtest.assembly.ctypefile.CompomnentTypeFileTestCase.typeFile3
> demonstrates this failure and is currently @Ignore(d)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
