Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: Java-M1
    • Fix Version/s: None
    • Component/s: Java SCA Samples
    • Labels:
      None
    • Environment:
      all

      Description

      The readme document that takes you to SCA samples consists primary of three levels. Required changes are:

      tuscany-incubating-M1-RC1/README.txt

      • Add Documentation reference
      • Add Getting started reference

      tuscany-incubating-M1-RC1/docs/sampleSetup.htm

      • helloworld/readme.htm Currently says "use JDK 1.5 java command with the previous jars.." but sampleSetup says you can go straight to samples if you have the binary release. So you don't get to know what jars are required.

      tuscany-incubating-M1-RC1/samples/sca/*/readme.htm

      • Doesn't actuall tell you what the previosu jars are as sampleSetup.htm it tells you to ignore the setup steps. Need and example of the command line to use
      • helloworld-SNAPSHOT.jar -> sample-helloworld-incubating-M1.jar
      • org.apache.tuscany.samples.helloworld.HelloWorldClient -> helloworld.HelloWorldClient
      • See helloworld-readme.htm.patch (attached)

      There's a good change that someone is in the middle of fixing the readmes but if you want me to go through them, fix them as above and provide patches, then let me know.

      1. helloworld-readme.htm.patch
        3 kB
        Simon Laws
      2. building.patch
        0.8 kB
        Kelvin Goodson
      3. README.htm
        2 kB
        Kelvin Goodson

        Activity

        Hide
        Simon Laws added a comment -

        patch to java/samples/sca/helloworld/readme.htm

        Show
        Simon Laws added a comment - patch to java/samples/sca/helloworld/readme.htm
        Hide
        Kelvin Goodson added a comment -

        In the windows source distribution, the top level BUILDING.txt file
        1) it tells you to cd to tuscany/java, but there is no need to cd anywhere, you are already there
        2) it references java 1.5.2_06 as ok, I have successfully built it with 1.5.0_06, so we could either list known compatible versions, or change the quoted version (on the basis that its likely that later versions will be OK)
        3) either in this file or in the top level README.txt file we could give an instruction to extract the distribution zip file under a path name with no spaces in. I initially extracted to C:\Documents and Settings\kg\My Documents\Tuscany\M1 and got a test case failure, which resolved when moving to a path with no spaces

        Show
        Kelvin Goodson added a comment - In the windows source distribution, the top level BUILDING.txt file 1) it tells you to cd to tuscany/java, but there is no need to cd anywhere, you are already there 2) it references java 1.5.2_06 as ok, I have successfully built it with 1.5.0_06, so we could either list known compatible versions, or change the quoted version (on the basis that its likely that later versions will be OK) 3) either in this file or in the top level README.txt file we could give an instruction to extract the distribution zip file under a path name with no spaces in. I initially extracted to C:\Documents and Settings\kg\My Documents\Tuscany\M1 and got a test case failure, which resolved when moving to a path with no spaces
        Hide
        Kelvin Goodson added a comment -

        here's one way of slicing/dicing the building.txt file

        Show
        Kelvin Goodson added a comment - here's one way of slicing/dicing the building.txt file
        Hide
        Simon Laws added a comment -

        The problem with samplesSetup.htm not discussing the list of jars in the case of the binary distro is resolved by changing the wording in readmes that mentioned "previous jars" to direcltly specify that the tuscany runtime jar and the sample jar are required on the classpath

        Show
        Simon Laws added a comment - The problem with samplesSetup.htm not discussing the list of jars in the case of the binary distro is resolved by changing the wording in readmes that mentioned "previous jars" to direcltly specify that the tuscany runtime jar and the sample jar are required on the classpath
        Hide
        Simon Laws added a comment -

        The helloworldjsonrpc sample readme.htm has the worng URL for starting the client. It should now be http://localhost:8080/sample-helloworldjsonrpc-incubating-M1/

        Show
        Simon Laws added a comment - The helloworldjsonrpc sample readme.htm has the worng URL for starting the client. It should now be http://localhost:8080/sample-helloworldjsonrpc-incubating-M1/
        Hide
        Simon Laws added a comment -

        The helloworldweb sample readme.htm has the worng URL for starting the client. It should now behttp://localhost:8080/sample-helloworldweb-incubating-M1/.
        It also has the wrong war name, it should be samples-helloworldweb-incubating-M1.war

        Show
        Simon Laws added a comment - The helloworldweb sample readme.htm has the worng URL for starting the client. It should now behttp://localhost:8080/sample-helloworldweb-incubating-M1/. It also has the wrong war name, it should be samples-helloworldweb-incubating-M1.war
        Hide
        Simon Laws added a comment -

        The helloworldwsclient readme should mention that the tuscany-axis2 jar is also required. Here is a sample command line for linux:

        java -cp ../../../lib/axis2/tuscany-axis2-incubating-M1.jar:../../../lib/tuscany-runtime-incubating-M1.jar:./target/sample-helloworldwsclient-incubating-M1.jar helloworld.HelloWorldClient

        Show
        Simon Laws added a comment - The helloworldwsclient readme should mention that the tuscany-axis2 jar is also required. Here is a sample command line for linux: java -cp ../../../lib/axis2/tuscany-axis2-incubating-M1.jar:../../../lib/tuscany-runtime-incubating-M1.jar:./target/sample-helloworldwsclient-incubating-M1.jar helloworld.HelloWorldClient
        Hide
        Kelvin Goodson added a comment -

        Here's a new redme file for the sdo/tools directory.

        Show
        Kelvin Goodson added a comment - Here's a new redme file for the sdo/tools directory.
        Hide
        ant elder added a comment -

        SDO tools readme applied. Thanks Kelvin!

        Show
        ant elder added a comment - SDO tools readme applied. Thanks Kelvin!
        Hide
        Simon Laws added a comment -

        No readme for...
        samples/sca/customerinfo
        samples/sca/helloworld-jms although there are readmes under client and server

        Show
        Simon Laws added a comment - No readme for... samples/sca/customerinfo samples/sca/helloworld-jms although there are readmes under client and server
        Hide
        Andrew Borley added a comment -

        If you follow the sampleSetup manual instructions for Tomcat, put all tuscany .war files into the tomcat/webapps directory and start tomcat, a number of ClassNotFoundExceptions are thrown. To fix these the following jars need to be added.
        In tomcat/common/lib add
        js-1.6R2.jar
        xbean-2.1.0.jar
        In tomcat/server/lib add
        tuscany-container-rhino-incubating-M1.jar

        These make Tomcat equivalent to the Tomcat generated by maven in testing/tomcat/readme.htm

        Show
        Andrew Borley added a comment - If you follow the sampleSetup manual instructions for Tomcat, put all tuscany .war files into the tomcat/webapps directory and start tomcat, a number of ClassNotFoundExceptions are thrown. To fix these the following jars need to be added. In tomcat/common/lib add js-1.6R2.jar xbean-2.1.0.jar In tomcat/server/lib add tuscany-container-rhino-incubating-M1.jar These make Tomcat equivalent to the Tomcat generated by maven in testing/tomcat/readme.htm
        Hide
        Jean-Sebastien Delfino added a comment -

        I'm not sure if these patches have been applied, just some of them? all of them? Rick, could you please check the status. Thanks...

        Show
        Jean-Sebastien Delfino added a comment - I'm not sure if these patches have been applied, just some of them? all of them? Rick, could you please check the status. Thanks...
        Hide
        Rick Rineholt added a comment -

        Looking through these they seem to be fixed.

        Show
        Rick Rineholt added a comment - Looking through these they seem to be fixed.

          People

          • Assignee:
            Rick Rineholt
            Reporter:
            Simon Laws
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development