Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • isn't <java.interface /> mandatory for a <service />?
    • removed the line and ran the test case and it passed
    • SL - No, if you remove the interface.java element the runtime will derive the interface by looking at the service implementation
  • <tuscany:binding.rmi uri="rmi://localhost:8099/CalculatorRMIService"/>
    • what does the uri attribute mean?
    • is it the uri where the service can be found? from what i understood tuscany will also deploy the service and make it available, what if the host is not localhost?
    • SL - you can use the uri to configure the binding to create the RMI endpoint at a certain address. If you omit it Tuscany should create a default endpoint address
      • FM - what if the binding.rmi uri inside a <service> specifies a host other than localhost? First of all, i believe that host should be "tuscany aware", but does tuscany know to make this kind of distributed deployments? If this is possible, please give more details.
      • Ant - i think ideally where possible we should try to avoid using absolute uri's in any of the Tuscany samples. And we should try to keep the composites as simple as possible too, so eg unless the sample is actually demonstrating how to override the defaults then probably it shouldn't even be specifiying the uri attribute instead just using the defaults.

sample-contribution-binding-sca-calculator

...