[
https://issues.apache.org/jira/browse/TUSCANY-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-3454.
---------------------------------
Resolution: Fixed
Fixed under r906398. The JMS broker and CORBA tnameserv are now started
automatically when the services that need them are launched.
> Launch procedure for travel sample servers is inconsistent
> ----------------------------------------------------------
>
> Key: TUSCANY-3454
> URL: https://issues.apache.org/jira/browse/TUSCANY-3454
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Travel Sample
> Reporter: Simon Nash
> Assignee: Simon Nash
>
> Some of the travel sample scenarios need a separate process to be started
> before the service is launched. This is confusing and error-prone.
> Specifically:
> launchers/currencyconverter-jms requires a JMS broker process to be started
> before running the launcher
> services/smsgateway-jms requires a JMS broker process to be started before
> running the service
> services/smsgateway-corba requires the CORBA tnameserv process to be
> started before running the service
> This is inconsistent with the other currencyconverter-* and smsgateway-*
> scenarios and is confusing and error-prone for users running these scenarios.
> Also, it means that these scenarios can't easily be run from the
> distribution tree, as there are no jar files in the distribution to run the
> JMS broker process or the CORBA tnameserv process.
> A suggested fix is to modify the launcher/bootstrap code for these scenarios
> to automatically start the required JMS broker or CORBA tnameserv before
> running the service launcher.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
