Readme of cluster demo contains following problems: Section 3, Build the client and service applications: change "cd quickstarts/demos/cluster" to "cd quickstarts/switchyard/demos/cluster" Section 3, Deploy services: change in all deploy statements "-Ddeploy.port" to "-Djboss-as.port"
Re: the instructions to build, this seems like a packaging/productization issue more than an issue with the quickstart documentation. The product is using a different location for the quickstarts than the project. Does "-Ddeploy.port" not work with the version of the AS deploy plugin packaged in the product? I don't have any issues using this property with EAP 6.1.
The "-Ddeploy.port" does not work with ER1. The default port is used: mvn -Ddeploy.port=10999 jboss-as:deploy INFO: JBoss Remoting version 3.2.12.GA [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 17.565s [INFO] Finished at: Tue Sep 03 23:54:21 CEST 2013 [INFO] Final Memory: 40M/483M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.4.Final:deploy (default-cli) on project switchyard-quickstart-demo-cluster-client: Could not execute goal deploy on /home/pdrozd/workspace/AS/jboss-eap-6.1-ER1/quickstarts/switchyard/demos/cluster/client/target/switchyard-quickstart-demo-cluster-client.jar. Reason: I/O Error could not execute operation '{ [ERROR] "address" => [], [ERROR] "operation" => "read-attribute", [ERROR] "name" => "launch-type" [ERROR] }': java.net.ConnectException: JBAS012144: Could not connect to remote://localhost:9999. The connection timed out [ERROR] -> [Help 1] [ERROR]
Ugh. Version of the maven plugin used in the community project is 7.1.1. Tom - can you have a look at this one and see if there's any harm in bumping jboss-as-maven-plugin to 7.4? If it's still good on the community side, let's align with what's being used in productization and update the Readme accordingly.
I went through and tested the quickstarts that had a Readme mentioning the jboss-as:deploy step, saw no issues. Submitted pull.
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1685 Tom - fix for this issue requires an update to the README in quickstarts/demo/cluster as well, right?
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1685 I went ahead and added the commit for quickstarts: https://github.com/jboss-switchyard/quickstarts/commit/ffd4b1475ab6cb7a73d83035dc20edd90fc79499
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1685 pushed
*** Bug 1018899 has been marked as a duplicate of this bug. ***
The first part of the bug description is not fixed: Section 3, Build the client and service applications: change "cd quickstarts/demos/cluster" to "cd quickstarts/switchyard/demos/cluster"
The project doesn't include a switchyard directory within quickstarts, so fixing the README upstream is not appropriate. I have reassigned to the build component in case prod wants to make an adjustment.
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1685 to Closed