[
https://issues.apache.org/jira/browse/TUSCANY-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843179#action_12843179
]
Simon Laws commented on TUSCANY-242:
------------------------------------
I committed the other 2.x changes under r920885. I'll add changes to 1.x also.
Here's the list of anyURI references in the 1.x XSDs
sca-binding-jms.xsd (5 matches)
39: <attribute name="initialContextFactory" type="anyURI"/>
40: <attribute name="jndiURL" type="anyURI"/>
62: <attribute name="name" type="anyURI" use="required"/>
80: <attribute name="name" type="anyURI" use="required"/>
90: <attribute name="name" type="anyURI" use="required"/>
sca-binding-webservice.xsd
30: <attribute name="wsdlElement" type="anyURI" use="optional"/>
sca-contributions.xsd
36: <attribute name="location" type="anyURI" use="optional"/>
sca-core.xsd (12 matches)
45: <attribute name="targetNamespace" type="anyURI" use="optional"/>
70: <attribute name="promote" type="anyURI" use="required" />
95: <attribute name="target" type="sca:listOfAnyURIs" use="optional"/>
99: <attribute name="promote" type="sca:listOfAnyURIs" use="required" />
143: <attribute name="file" type="anyURI" use="optional"/>
156: <attribute name="uri" type="anyURI" use="optional"/>
247: <attribute name="target" type="sca:listOfAnyURIs" use="optional"/>
279: <attribute name="source" type="anyURI" use="required"/>
280: <attribute name="target" type="anyURI" use="required"/>
309: <attribute name="targetNamespace" type="anyURI"/>
344: <simpleType name="listOfAnyURIs">
345: <list itemType="anyURI"/>
sca-definitions.xsd
21: <attribute name="targetNamespace" type="anyURI" use="optional"/>
sca-implementation-spring.xsd
19: <attribute name="location" type="anyURI" use="required"/>
sca-interface-wsdl.xsd (2 matches)
17: <attribute name="interface" type="anyURI" use="required"/>
18: <attribute name="callbackInterface" type="anyURI" use="optional"/>
tuscany-sca-binding-notification.xsd (2 matches)
37: <attribute name="ntm" type="anyURI" use="optional"/>
38: <attribute name="notificationType" type="anyURI" use="optional"/>
tuscany-sca-binding-rmi.xsd (2 matches)
37: <attribute name="host" type="anyURI" use="optional"/>
39: <attribute name="serviceName" type="anyURI" use="optional"/>
tuscany-sca-contributions.xsd (2 matches)
31: <attribute name="uri" type="anyURI" use="required"/>
40: <attribute name="uri" type="anyURI" use="required"/>
tuscany-sca-implementation-resource.xsd
37: <attribute name="location" type="anyURI" use="required"/>
tuscany-sca-implementation-script.xsd
37: <attribute name="script" type="anyURI" use="optional"/>
tuscany-sca-implementation-widget.xsd
37: <attribute name="location" type="anyURI" use="required"/>
tuscany-sca-implementation-xquery.xsd
37: <attribute name="location" type="anyURI" use="required"/>
> SCDL loader should trim the whitespaces when the element text is parsed
> -----------------------------------------------------------------------
>
> Key: TUSCANY-242
> URL: https://issues.apache.org/jira/browse/TUSCANY-242
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
> Affects Versions: Java-M1
> Reporter: Raymond Feng
> Assignee: Simon Laws
> Fix For: Java-M1, Java-SCA-M2
>
>
> SCDL loader should trim the whitespaces when the element text is parsed.
> If I use the following SCDL section:
> <entryPoint name="InteropDocService">
> <interface.wsdl
> interface="http://soapinterop.org/#DocTestPortType"; />
> <binding.ws port="http://soapinterop.org/#interopDocPort"; />
> <reference>
> InteropDocServiceComponent/DocTestPortType
> </reference>
> </entryPoint>
> The \t, \n will show up as follows and the lookup will fail.
> targetURI= ServiceURIImpl (id=119)
> address=
> "sca:////\n\t\t\tInteropDocServiceComponent/DocTestPortType\n\t\t"
> isParsed= true
> isSCAScheme= Boolean (id=124)
> moduleComponentName= ""
> partName= "\n\t\t\tInteropDocServiceComponent"
> serviceName= "DocTestPortType\n\t\t"
> Note:
> The following format works fine.
> <reference>InteropDocServiceComponent/DocTestPortType</reference>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
