THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
...
- ran mvn jetty:run, opened _http://localhost:8080/sample-store-webapp/_
and i'm getting "TypeError: Cannot call method 'get' of undefined"
...
- the above questions have risen after trying to learn about tuscany exclusively browsing the website and the samples. meanwhile, i found the osoa website and specifications http://osoa.org/display/Main/Service+Component+Architecture+Specifications which i read after going through the samples and helped me answer many of my questions (especially the annotation ones). maybe it will be a good idea to have a special page on the tuscany website which would contain the up-to-date specifications from osoa. the documents were really helpful.
- i think one question that comes to your mind when reading about tuscany would be what overhead does for example <binding.ws/> add to an application. how much heavyweight/lightweight is each binding. what infrastructure do they use (e.g. jms). covering these aspects in the documentation would be very useful for a person reading about tuscany for the first time.