Runtime installer on OS X + EAP 6.1 looks fine.

The following quick starts are fine:

bean-service

bpel-service/jms_binding

bpel-service/loan_approval

bpel-service/say_hello

bpel-service/simple_correlation

bpm-service

camel-amqp-binding

camel-binding

camel-bus-cdi

camel-ftp-binding (but beware of SWITCHYARD-1810)

camel-jaxb

camel-jms-binding

camel-jpa-binding

camel-netty-binding (but need to use standalone-full.xml for TCP; see SWITCHYARD-1812)

camel-quartz-binding

camel-service

camel-soap-proxy

camel-sql-binding

ear-deployment

http-binding

These quick starts don't work for me:

bpel-service/xts_subordinate_wsba  (SWITCHYARD-1808)

bpel-service/xts_wsat                        (SWITCHYARD-1808)

More soon

Doug

Tested Forge on OS X and Fedora.        Found two issues :

https://issues.jboss.org/browse/SWITCHYARD-1809

https://issues.jboss.org/browse/SWITCHYARD-1811

Added a note on the workaround into SWITCHYARD-1809.

Starting the Quickstarts from the back end of the list on Fedora.

Tested on Fedora / EAP 6.1 GA :

rules-interview

rules-interview-container

rules-interview-dtable

soap-addressing

soap-attachment

soap-binding-rpc

transform-jaxb

transform-json

transform-smooks

transform-xslt

validate-xml

All work fine.

soap-mtom seems to have an issue in the jboss-as:deploy step where the tests run, and seem to need port 8080, which is taken by the EAP container that was started in the previous step.      If I do mvn -Dmaven.test.skip=true jboss-as:deploy, I'm able to deploy and run the executable client.

Do we need to support 6.0 Alpha and 6.0 GA still? The installer does not work due to no module layering in those versions. Besides our deployment code is built upon EAP6.1 BOM and the binaries will not be compatible with these versions.

Used installer on fedora 17, with EAP 6.1, worked fine.

Installed BPEL console - had to download tools zip and install from filesystem due to authentication issue when using URL to jenkins. Console seems to work fine.

Found the same issue as Doug with the XTS examples. However there are a number of issues with these:

1) Example standalone-xts.xml is out of date - and assuming the only change is to add the xts module, this should possibly be described in the quickstart readme, rather than using the example file.

2) The referenced wiki docs are out of date as well - probably better to include all the steps in the readme.

However not sure what the underlying problem is with using jboss-as:deploy on these, so would suggest dropping these from the distribution for now until we can get them updated?

• OS
  • Windows 7 professional
• EAP
  • 6.1.0 GA
• Installation
  • Bundle zip -
  • Installer - README.txt needs update, the BPEL console and Forge tooling are no longer optionally asked rather installed manually (will be fixed via SWITCHYARD-1816)
    • Runtime only -
    • BPEL console -
      • BTW, how to install BPEL console to domain mode, manual?
• Verify console works - shows application and metrics
  • BPEL console - History Query does not show any process ids in the dropdown, after running bpel-service/loan-approval QS, is it supposed to work like that?
  • Admin Console -
    
• Test domain mode deployment in EAP
• Tests
  • rest-binding - (both in standalone and domain modes)
  • demo/orders -
  • demo/helpdesk -
  • demo/policy-security-basic -

• OS
  • RHEL 6.1
• EAP
  • 6.1.0.GA
• Installation
  • Installer
    • Needed to use newer version of ant, otherwise xmlns="" is added to the configuration files.
    • Runtime: all good using ant 1.9.1. (I added a note to the documentation.)
    • BPEL console: same as others have reported (i.e. needed to download separately and update installer.properties)
• Quickstarts (also verified message transmission using console)
  • bean-service
  • camel-jaxb
  • transform-json (no services) - empty targetNamespace
  • soap-attachment- empty targetNamespace
  • demos/orders - no metrics calculated, URL in readme is incorrect (deployed war does not include version)
  • demos/helpdesk - empty targetNamespace, readme could add bits on how to bring up the BAM page

• Quickstarts
  • demos/policy-transaction - enabled throttling
  • jca-inflow-activemq

• OS
  • Windows 7 professional
• EAP
  • 6.1.0 Alpha1
• Installation
  • Bundle zip -
  • Installer
    • Runtime only - failed to copy JBossWS jars, will be fixed via SWITCHYARD-1816
    • BPEL console -
• Verify console works - shows application and metrics
  • BPEL console - History Query shows process ids in the dropdown
  • Admin Console -
• Test domain mode deployment in EAP
• Tests
  • rest-binding - (both in standalone and domain modes)
  • demo/orders -
  • demo/helpdesk -
  • demo/policy-security-basic -

• OS
  • Fedora 19
• EAP
  • 6.1.0 Alpha
  • 6.1.1
• Installation
  • Bundle zip
• Tests
  • by manual instruction
    • remote-invoker
    • demos/cluster
    • demos/transaction-propagation
  • Arquillian testcase
    • jca-{inflow,outbound}-{activemq,hornetq}
    • demos/policy-transaction

I found one issue on both of jca-inflow-{activemq,hornetq} quickstarts - I'm pretty sure it's an application bug around JAXB transformation. I thought It has been fixed but still there...

[SWITCHYARD-1817] JAXB transformation fails in jca-inflow quickstarts - JBoss Issue Tracker

Others work fine.