0.1 Release is Staged - Please Test!

[kcbabo]

Tom just closed the staging repository for 0.1, which means it's available for everyone to download and test.

AS7 Distribution

AS6 Distribution

Please download both distributions and install (i.e. unzip) them and deploy the demo/orders quickstart.  For bonus points, pull up the WS in the quickstart using SoapUI and do an end-to-end test.  I would like to get confirmation that both releases work on OSX, Fedora, and Windows.

Thanks!

[tfennelly]

I created a Getting Started Guide... if we can follow this and make sure it's not missing any steps or misleading in any way: https://docs.jboss.org/author/display/SWITCHYARD/Home

[kcbabo]

Thanks, Tom!  I scanned it real quick and it looks quite nice.  I will walk through the instructions this morning to verify that everything works.

cheers,

keith

[tfennelly]

To build the quickstarts, you'll need to add the following <mirror> to the <mirrors> section of your settings.xml (~/.m2/settings.xml):

<settings>

    <!-- Other settings.... -->

    <mirrors>
        <!-- Other mirrors.... -->

          <mirror>
                <id>jboss-staging-repository-group</id>
                <mirrorOf>*</mirrorOf>
                <name>JBoss.org Staging Repository Group</name>
                <url>https://repository.jboss.org/nexus/content/groups/staging/</url>
        </mirror>
    </mirrors>

</settings>

[kcbabo]

A couple of people have mentioned that the quickstarts fail due to missing maven artifacts.  This is due to the fact that the 0.1 artifacts have only been published in the staging repository and are not visible through the usual public group in the JBoss nexus instance.  To address this, you can add the following mirror definition to your ~/.m2/settings.xml:

<mirrors>
  <mirror>
     <id>jboss-staging-repository-group</id>
     <mirrorOf>*</mirrorOf>
     <name>JBoss.org Staging Repository Group</name>
     <url>https://repository.jboss.org/nexus/content/groups/staging/</url>
   </mirror>
</mirrors>

[kcbabo]

BTW, you will not need this setting once we verify and "release" the staged artifacts.  This is just a temporary setting while the artifacts are staged.

[kcbabo]

Just to keep the community in the loop, I'll summarize where we're at right now:

The AS6 release build has been verified on Fedora, OSX, and Windows.  There was one report of a Windows issue with the AS6 build, but I verified the release myself on Windows just now.

The AS7 release build has been verified on Fedora and OSX.  There is an issue with file path encoding on Windows that causes all deployments to fail (SWITCHYARD-276).  For 0.1, Windows users should use the AS6 build as a workaround.

I will push the release tonight.

[antollinim]

The reason why I had an issue with AS6 in Windows was because I did not write the SOAP request myself (as explained here). I just let soapUI genererate a sample SAOP request (based on the WSDL) and I just added the missing valaues (orderId, itemId and quantity). When I sent the SOAP message it failed with an Exception.

I just then copied and pasted the sample request and it worked out of the box.

So the problem seems to be that the WSDL does not describe the service in a proper way. Without manual intervention the request fails.

So, is this a bug?

[kcbabo]

I just tried this with SoapUI generating the request and it worked fine on AS6.  Which version of SoapUI are you using?  Can you post what the request message looks like?

[antollinim]

I was not able to reproduce the error now... The auto-generated SOAP message works ok out of the box.

I must have done something wrong the first time. Sorry for the confusion