--------------------------------------------------------------
|                                                            |
|	Dear,                                                  |
|                                                            |
|	Thanks for downloading the DyReS source code.          |
|                                                            |
|	The quickstart guide below will allow you to be up     |
|	and running in no time.                                |
|                                                            |
|	Best,                                                  |
|                                                            |
|	The DyReS team.                                        |
|                                                            |
--------------------------------------------------------------

********************
* DyReS Quickstart *
********************

Step 1: Create and configure Eclipse projects
---------------------------------------------

Extract the .zip file into your Eclipse folder. This will create 4 
folders (dyres.jbossaop, dyros.jbossaop.test, dyres.springaop and
dyres.springaop.test) and the license file (COPYING.txt) under which 
this software has been put available.

Create in Eclipse 4 new projects according to the 4 folders:
  - Java project with name "dyres.jbossaop"
  - JBossAOP project with name "dyres.jbossaop.test"
  - Java project with name "dyres.springaop"
  - Java project with name "dyres.springaop.test"

For each of the projects, you have to include all .jar files in the 
/lib directory via the Project > Properties > Java build path and
make sure that the source folder points to <project name>/src.

Note that the JBoss AOP update site for Eclipse is the following:
http://download.jboss.org/jbosside/updates/stable.

Step 2: Run test applications
-----------------------------

The test applications to add, replace and remove a tracing aspect
in a JBoss AOP setting can be found in test.local.tracing.testapp:
AddLoggerTest, ReplaceLoggerTest and RemoveLoggerTest.

  - Start the main() of these applications
  - Load the application by entering "1" + enter in the console
  - Start the application by entering "2" + enter
  - Execute the reconfiguration by entering "3" + enter

Test applications to add, replace and remove a tracing aspect in
a Spring AOP can be executed in a similar way.

The test applications to add, replace and remove encoding/
decoding or fragmentation/reassembling support (both the
fin-act and the act-fin versions) consist of two applications.
In the JBoss AOP case, these test applications can be found in
test.distr.encoding.testapp.local and test.distr.fragmentation.
testapp.local. The addition of a compression/decompression
service is described into more detail nest. Other reconfigurations
can be executed similarly.

  - Start the main() of AddEncoderLocalTest and AddDecoderLocalTest
  - Load first the application where the decoder is used (server-side), 
    then the encoder counterpart (client-side) (by entering "1" + 
    enter in both consoles)
  - Start the application by entering "2" + enter in the console
    of the application using the encoder (client-side)
  - Execute the reconfiguration by entering "3" + enter in both
    consoles

Step 3: Run JUnit tests
-----------------------

The test suites for dyres.jbossaop can be found in

  - test.local.tracing.junit.DyReSJBossAOPTestSuite for the 
    reconfigurations for adding, replacing and removing a
    tracing aspect
  - test.distr.encoding.junit.DyReSJBossAOPTestSuite for the 
    reconfigurations for adding, replacing and removing an
    encoding/decoding service

The test suites for dyres.springaop can be found in

  - test.local.tracing.junit.DyReSSpringAOPTestSuitefor the 
    reconfigurations for adding, replacing and removing a
    tracing aspect
  - test.distr.encoding.junit.DyReSSpringAOPTestSuite for the 
    reconfigurations for adding, replacing and removing an
    encoding/decoding service

Note that these tests don't execute dynamic reconfigurations. 
Their goal is to control if the used scripts contain errors.