THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Note | ||
|---|---|---|
| ||
Note that binding.corba is still under development and may not be yet available in Tuscany releases. |
<binding<binding.corba>
The Tuscany Java SCA runtime supports CORBA using the <binding.corba> SCDL extension. New CORBA based service can be provided using a <binding.corba> element within a SCA <service>, existing CORBA object can be accessed using a <binding.corba> element within a SCA <reference>.
...
| Note | ||
|---|---|---|
| ||
When using Tuscany service/reference binding to communicate with traditional CORBA objects: 1. Don't overload method names in Java interface. 2. Don't create methods with names which differs only by case, ie. you shouldn't declare both methods: caseSensitive() and CaseSensitive(). You can ignore above rules if you are using Tuscany CORBA binding to communicate with other Tuscany CORBA binding. Those constraints results from differences between IDL and Java. More details can be found in "Method/operation mapping rules" section. |
...
| Note | ||
|---|---|---|
| ||
Exceptions declared by user should be named to match remote exception ID. Example: if in reference binding remote object throws exception with ID "IDL:org/apache/tuscany/sca/test/corba/generated/WrongColor:1.0" then you should declare exception class named "org.apache.tuscany.sca.test.corba.generated.WrongColor". The same in service bindings. SCA component exception will be thrown with ID created from Java name. |
...