[
https://issues.apache.org/jira/browse/TUSCANY-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-3423.
---------------------------------
Resolution: Fixed
Fixed by commits r902059 and r902061, using the approach suggested in the issue
description.
> The travel sample domain/node scenarios can't be run from the distribution
> jars
> -------------------------------------------------------------------------------
>
> Key: TUSCANY-3423
> URL: https://issues.apache.org/jira/browse/TUSCANY-3423
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Travel Sample
> Reporter: Simon Nash
> Assignee: Simon Nash
>
> The travel sample has two launchers that use a domain manager with separate
> execution nodes (introducing-domain and fullapp-domain). These launchers
> don't work when run from the distribution directory.
> This problem is caused by two issues:
> 1. The domain configuration file workspace.xml uses relative paths that only
> work in the development build directory structure.
> 2. The domain manager needs to find its configuration files on the file
> system, not packaged in jars.
> The following approach is suggested to fix this problem:
> 1. Create a "domain-config" directory in the distribution tree and place the
> configurations for introducing-domain and fullapp-domain under "introducing"
> and "fullapp" subdirectories of this "domain-config" directory.
> 2. Create a separate copy of workspace.xml for use in the distribution
> build, located in a subdirectory "distribution" under the src/main/resources
> directory of each module that needs it (currently introducing-domain and
> fullapp-domain). The maven build would copy this version of workspace.xml to
> the distribution tree instead of the default version that uses the
> development build directory structure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
