Bug 1016053 - FSW 6.0.0 ER4 switchyard/demos/orders Readme.md steps inconsistent with other quickstarts
Summary: FSW 6.0.0 ER4 switchyard/demos/orders Readme.md steps inconsistent with other...
Keywords:
Status: MODIFIED
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Examples
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-07 12:08 UTC by ppecka
Modified: 2021-11-08 10:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The wording of the switchyard/demos/orders Readme.md file was inconsistent with those of the other quick starts. To see amended instructions, please refer to the bug ticket.
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description ppecka 2013-10-07 12:08:53 UTC
Description of problem:
Please update Readme file for switchyard/demos/orders with appropriate maven goals which should be taken to deploy application. There is no need to manually copy built war file when jboss-as plugin is configured in pom.xml, this can be copy&pasted for example from quickstarts/switchyard/bean-service/Readme.md mainly:

Running the quickstart
======================

JBoss AS 7
----------
1. Build the quickstart:

        mvn clean install

2. Start JBoss AS 7 in standalone mode:

        ${AS}/bin/standalone.sh

3. Deploy the Quickstart :

        mvn jboss-as:deploy

4. Submit a webservice request to invoke the SOAP gateway.  There are a number of ways to do this :
      - Submit a request with your preferred SOAP client - src/test/resources/xml contains sample
        requests and the responses that you should see
      - Use the simple bundled SOAP client and the sample request XML e.g.
<br/>
```
            mvn exec:java


Version-Release number of selected component (if applicable):
soa-6.0.0-ER4

Comment 1 Douglas Palmer 2014-10-08 05:27:41 UTC
Out of date. This was fixed long ago.


Note You need to log in before you can comment on or make changes to this bug.