Hi Nigel,
Thanks for including the example clearly.
It appears that the "external" element does not have a terminating slash.
Since we don't want to bloat the system with a full run-time
schema/DTD-based parser, we don't catch those type of errors at runtime
in the most intelligent way. One of our roadmap items is an offline
parser that uses a parser libary that is extremely picky and clear in
its errors.
Jim
On 3/6/12 7:03 PM, Merritt, Nigel (Contractor) wrote:
*UNCLASSIFIED*
Hi,
I'm attempting to create a GUI application as the main application for
an OpenCPI based system. Looking at the documentation, in order to
route test/debug data to the main app I need to connect the main app
to an RCC worker port using an external port.
My app creates the workers and connection using the XML string method,
however I can't seem to connect up an external port using this
method. There is an example in Hello App:
" <connection>"
" <external name='out'/>"
" <port instance='hello' name='out'/>"
" </connection>"
But trying to replicate this in my main app XML string...
" <connection>"
" <external name='data'>"
" <port instance='process_results' name='data'/>"
" </connection>"
...yields the error: "Error parsing assembly xml string due to: no
ports found under connection".
The XML body and spec of my component are below.
<RccImplementation controloperations="start">
<xi:include href="process_results_spec.xml"/>
</RccImplementation>
<ComponentSpec Name="process_results">
<DataInterfaceSpec Name="data" Producer="false">
<xi:include href="stream_protocol.xml"/>
</DataInterfaceSpec>
</ComponentSpec>
So to be specific:
1. Does the external port need to be declared in the component spec /
body and if so what is the syntax used?
2. What is the syntax used in the main app XML to connect to the
external port (assuming the above is incorrect)?
Many thanks,
Nigel Merritt
*IMPORTANT*: This email remains the property of the Department of
Defence and is subject to the jurisdiction of section 70 of the Crimes
Act 1914. If you have received this email in error, you are requested
to contact the sender and delete the email.
_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
_______________________________________________
opencpi_dev mailing list
[email protected]
http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
