[
https://issues.apache.org/jira/browse/TUSCANY-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571073#action_12571073
]
Mike Edwards commented on TUSCANY-2052:
---------------------------------------
The SCA Assembly spec says that a composite MUST have a targetNameSpace
declared.
The spec does not say that the runtime should raise an error in the case of the
targetNameSpace being absent, but that would be my expectation.
Does anyone think that the spec is wrong in this area? The problem is a
general one for XML artifacts - if they don't belong to a namespace, how can
you senssibly search for them. It's like a Java class that is not part of a
package....
So my suggestion is to fix this JIRA by changing the composite loading code to
throw an exception if the composite has no targetNameSpace declared.....
> A Composite without a targetNamespace is not properly started in a
> contribution
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-2052
> URL: https://issues.apache.org/jira/browse/TUSCANY-2052
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.0
> Environment: All
> Reporter: Hasan Muhammad
> Fix For: Java-SCA-Next
>
>
> If the composite does not have a targetNamespace, then the composite QName in
> the sca-contribution.xml file would just be the localname. In this case, when
> we add the contribution and start the deployables, it seems they are not
> properly being started, since none of the service can be found through
> lookup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
