diff --git a/CONTRIBUTING.html b/CONTRIBUTING.html deleted file mode 100644 index 7ea8b10285..0000000000 --- a/CONTRIBUTING.html +++ /dev/null @@ -1,39 +0,0 @@ -

JBoss AS Quickstarts

-

Quickstarts (or examples, or samples) for JBoss AS. There are a number of rules for quickstarts:

- -

You can find the documentation at https://docs.jboss.org/author/display/AS7/Documentation.

-

If you add a quickstart, don't forget to update dist/src/main/assembly/README.md.

-

The 'dist' folder contains Maven scripts to build a zip of the quickstarts.

-

The quickstart code is licensed under the Apache License, Version 2.0: -http://www.apache.org/licenses/LICENSE-2.0.html

-

Quickstarts in other repositories

-

If your quickstarts are stored in another repository, you may wish to merge them in from there, rather than contribute them from source. If you plan to do this, discuss first with the JBoss AS Quickstarts team, as they will want to review all commits to your repo going forward.

-

To do this

-
    -
  1. -

    Add the other repo as a remote

    -

    git remote add -f

    -
    2. -
  2. -

    Merge from the tag in the other repo that you wish to use. It is important to use a tag, to make tracking of history easier. We use a recursive merge strategy, always preferring changes from the other repo, in effect overwriting what we have locally.

    -

    git merge -s recursive -Xtheirs --no-commit

    -
    3. -
  3. -

    The merge is not committed, so any updates to the README.md and parent POM can be made. Having made these, perform the merge. We suggest updating the commit message to "Merge ''".

    -

    git commit

    -
    4. -
  4. -

    Review and push to upstream

    -

    git push upstream HEAD:master

    -
    5. -
\ No newline at end of file diff --git a/README.html b/README.html deleted file mode 100644 index cf7e770546..0000000000 --- a/README.html +++ /dev/null @@ -1,128 +0,0 @@ -

JBoss AS Quickstarts

-

These quickstarts will run in both the JBoss AS 7 or JBoss Enterprise Application Platform 6 environments. Check the README.md file in each quickstart folder for more details and specific instructions.

-

If you want to run the quickstarts in JBoss EAP, we recommend using the JBoss EAP zip. This version chooses the exact dependencies used in EAP and ensures you test and compile against your runtime environment.

-

Available Quickstarts

-

These are the quickstarts for JBoss AS 7 and JBoss Enterprise Application Platform 6. You will find detailed tutorials in the -various guides at https://docs.jboss.org/author/display/AS7

-

Quickstarts with tutorials in the Getting Started Developing Applications Guide -are noted with two asterisks ( ** ) following the quickstart name.

- -

Prerequisites

-

To run these quickstarts with the provided build scripts, you will need the following:

-
    -
  1. Java 1.6, to run JBoss AS and Maven. You can choose from the following: -
    2. -
  2. -

    Maven 3.0.0 or newer, to build and deploy the examples

    - -
    3. -
  3. -

    The JBoss AS 7 distribution zip or the JBoss Enterprise Application Platform 6 distribution zip

    - -
    4. -
-

You can also deploy the quickstarts from Eclipse using JBoss tools. For more information on how to set up Maven and the JBoss tools, refer to the Getting Started Developing Applications Guide.

-

JBoss AS 7 Quickstart Instructions

-

If you are using the JBoss AS 7 Quickstart distribution, the community artifacts are available in the Maven central repository so no additional configuration is needed.

-

JBoss Enterprise Application Platform 6 Quickstart Instructions

-

If you are using the JBoss Enterprise Application Platform 6 distribution, you will need to download and configure the Maven repository.

-
    -
  1. -

    Download the JBoss Enterprise Application Platform 6 Maven repository distribution zip and unzip it into a directory of your choice.

    -
    2. -
  2. -

    Modify the example-settings.xml file located in the root of your quickstarts folder. Replace all instances of 'path/to/jboss-eap/repo' within '<url>file:///path/to/jboss-eap/repo</url>' with the fully qualified path to the Maven repository you unzipped in the previous step.

    -
    3. -
  3. -

    When you run Maven commands, you will need to append '-s PathToQuickstarts/example-settings.xml' to the command, for example:

    -
    -

    mvn jboss-as:deploy -s PathToQuickstarts/example-settings.xml

    -
    -
    4. -
  4. -

    If you do not want to specify the alternate path for your user settings on every Maven command, you can configure your user settings as follows:

    - -
    5. -
-

Building and Deploying the Quickstarts

-

To build and deploy a quickstart, in most cases you will do the following:

-
    -
  1. -

    Start the JBoss application server.

    -
    2. -
  2. -

    In a shell prompt, navigate to the root of the quickstart you want to run.

    -
    3. -
  3. -

    Type the following:

    - -
    4. -
  4. -

    See the README file in the individual quickstart folder for specific information on how to run and access the example.

    -
    5. -
\ No newline at end of file diff --git a/bean-validation/README.html b/bean-validation/README.html deleted file mode 100644 index b6e2480dd6..0000000000 --- a/bean-validation/README.html +++ /dev/null @@ -1,56 +0,0 @@ -

bean-validation: Bean Validation via Arquillian Example

-

Author: Karel Piwko kpiwko@redhat.com

-

What is it?

-

This is your project! It's a sample, Maven 3 project to help you -get your foot in the door developing with Java EE 6 on JBoss AS 7 or JBoss Enterprise Application Platform 6. -This project is setup to allow you to use CDI 1.0, JPA 2.0 and Bean Validation 1.0. -It includes a persistence unit and some sample persistence code to help -you get your feet wet with database access in enterprise Java.

-

It does not contain an user interface layer. The main purpose of the project is -to show you how to test Bean Validation with Arquillian. If you want to see an -example how to test Bean Validation via an user interface, check out Kitchensink -example available at https://github.com/jbossas/quickstart/tree/master/kitchensink.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

Running the Arquillian tests

-

By default, tests are configured to be skipped. The reason is that the sample -test is an Arquillian test, which requires the use of a container. You can select either -managed or remote container, the difference is that the remote one requires a running JBoss AS 7 / -JBoss Enterprise Application Platform 6 instance prior executing tests.

-

Testing on Remote Server

-

First you need to start JBoss AS 7 or JBoss Enterprise Application Platform 6 instance. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

Once the instance is started, run the test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-remote
-
-

Testing on Managed Server

-

Arquillian will start the container for you. All you have to do is setup a path to your JBoss AS7 or JBoss -Enterprise Application Platform 6. To do this, run

-
export JBOSS_HOME=/path/to/jboss-as
-
-

or if you are using Windows

-
set JBOSS_HOME=X:\path\to\jboss-as
-
-

To run the test in JBoss AS 7 or JBoss EAP 6, run the test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-managed
-
-

Investigating console output

-

JUnit will present you test report summary:

-
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0
-
-

If you are interested in more details, check target/surefire-reports directory. -You can check console output to verify that Arquillian had really used the real application server. -Search for lines similar to the following ones in the server output log:

-
 [timestamp] INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "test.war"
- ...
- [timestamp] INFO [org.jboss.as.server] (management-handler-threads - 1) JBAS018559: Deployed "test.war"
- ...
- [timestamp] INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment test.war in 48ms
- ...
- [timestamp] INFO [org.jboss.as.server] (management-handler-threads - 1) JBAS018558: Undeployed "test.war
-
\ No newline at end of file diff --git a/bmt/README.html b/bmt/README.html deleted file mode 100644 index 48f38b4aae..0000000000 --- a/bmt/README.html +++ /dev/null @@ -1,67 +0,0 @@ -

bmt (Bean Managed Transactions): Stepping Outside the Container (with JPA and JTA)

-

Author: Mike Musgrove

-

What is it?

-

On occasion the application developer requires finer grained control over the lifecycle of -JTA transactions and JPA Entity Managers than the defaults provided by the JEE container. -This example shows how the developer can override these defaults and take control of aspects -of the lifecycle of JPA and transactions.

-

[But note that a JEE container is designed with robustness in mind so you should -carefully analyse the scaleabiltiy, concurrency and performance needs of you application -before taking advantage of these techniques in your own applications.]

-

The example demonstrates how to manually manage transaction demarcation whilst accessing -JPA entities in JBoss AS 7:

- -

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
    $JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
    $JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
    mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
    mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-bmt.war to the running instance of the AS.

-

The application will be running at the following URL http://localhost:8080/jboss-as-bmt/BMT.

-

To undeploy from JBoss AS, run this command:

-
    mvn jboss-as:undeploy
-
-

If you need to redeploy the war then ensure that you explicitly undeploy it first so that databases -are cleaned up correctly.

-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the -Getting Started Developing Applications Guide -for more information.

-

Using the application

-

JBoss AS 7 comes with an H2 datasource by default. The example shows how to transactionally -insert key value pairs into to this H2 database and demonstrates the requirements on the -developer with respect to the JPA Entity Manager.

-

To access the application type the following into a browser:

-
    http://localhost:8080/jboss-as-bmt/BMT
-
-

You will be presented with a simple form for adding key value pairs and a checkbox to indicate -whether the updates should be executed using an unmanaged component (effectively this will run the transaction -and JPA updates in the servlet - ie not session beans). If the box is checked then the updates will be -executed within a session bean method.

-

To list all pairs leave the key input box empty. To add or update the value of a key fill in -the key and value input boxes. Press the submit button to see the results.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
    mvn dependency:sources
-    mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/cdi-injection/README.html b/cdi-injection/README.html deleted file mode 100644 index f8fa114001..0000000000 --- a/cdi-injection/README.html +++ /dev/null @@ -1,32 +0,0 @@ -

cdi-injection: Example Using CDI (Contexts and Dependency Injection)

-

Author: Jason Porter

-

What is it?

-

This example demonstrates the use of CDI 1.0 Injection and Qualifiers in JBoss AS 7 or JBoss Enterprise Application Platform 6 -with JSF as the front-end client.

-

You can test the output at the URL http://localhost:8080/jboss-as-cdi-injection

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the Application

-

First you need to start JBoss AS 7 or JBoss Enterprise Application Platform 6. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn clean package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-cdi-injection.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-cdi-injection/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

\ No newline at end of file diff --git a/cmt/README.html b/cmt/README.html deleted file mode 100644 index 305e8380a4..0000000000 --- a/cmt/README.html +++ /dev/null @@ -1,100 +0,0 @@ -

cmt (Container Managed Transactions): Example Using Transactions That Are Managed by the Container

-

Author: Tom Jenkinson

-

What is it?

-

This example demonstrates using transactions managed by the container. It is a fairly typical -scenario of updating a database and sending a JMS message in the same transaction. A simple -MDB is provided that prints out the message sent but this is not a transactional MDB and is -purely provided for debugging purposes.

-

Aspects touched upon in the code:

-
    -
  1. XA transaction control using the container managed transaction annotations
    2. -
  2. XA access to a H2 database using the JPA API
    3. -
  3. XA access to a JMS queue
    4. -
-

What are container managed transactions?

-

Prior to EJB, getting the right incantation to ensure sound transactional operation of a users -business logic was a highly specialised skill. Although this still holds true to a great -extent, EJB has provided a series of improvements to to allow simplified transaction demarcation -notation that is therefore easier to read and test. With CMT, the EJB container sets the -boundaries of a transaction, this differs from BMT (bean managed transactions) where the developer -is responsible for initiating and completing a transaction via the methods begin, commit, rollback -on a javax.transaction.UserTransaction.

-

What makes this an example of container managed transactions?

-

Take a look at org.jboss.as.quickstarts.cmt.ejb.CustomerManagerEJBImpl. You can see that -this stateless session bean has been marked up with an @javax.ejb.TransactionAttribute annotation.

-

The available options for this annotation are as follows:

- -

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

Testing the application

-

Executing the following command will build and test the application using Arquillian: -JBOSS_HOME= mvn clean test -Parq-jbossas-managed -NOTE: If you get the following you have not exported JBOSS_HOME: -Tests in error: - TestManagedBeanCustomerManager: jbossHome 'null' must exist

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6) with a JMS connection factory and a queue named -test queue in it. The instructions for this vary slightly depending upon whether you are using -the community release (JBoss AS 7) or the platform release (JBoss Enterprise Application Platform 6).

-

For JBoss AS 7: - $JBOSS_HOME/bin/standalone.sh -c standalone-full.xml -or if you are using JBoss AS 7 on windows - $JBOSS_HOME/bin/standalone.bat -c standalone-full.xml

-

For JBoss Enterprise Application Platform 6: - $JBOSS_HOME/bin/standalone.sh -or if you are using JBoss Enterprise Application Platform 6 on windows - $JBOSS_HOME/bin/standalone.bat

-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
    mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
    mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-cmt.war to the running instance of the AS.

-

The application will be running at the following URL http://localhost:8080/jboss-as-cmt/.

-

After a user is successfully added to the database, a message is produced container the -details of the user. An example MDB will dequeue this message and print the contents as such:

-
    Received Message: Created customer named: Tom with ID: 1
-
-

To undeploy from JBoss AS, run this command:

-
    mvn jboss-as:undeploy
-
-

If you need to redeploy the war then ensure that you explicitly undeploy it first so that databases -are cleaned up correctly.

-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

-

Using the application

-

JBoss AS 7 comes with an H2 datasource by default. The example shows how to transactionally -insert key value pairs into to this H2 database and demonstrates the requirements on the -developer with respect to the JPA Entity Manager.

-

To access the application type the following into a browser:

-
    http://localhost:8080/jboss-as-cmt/
-
-

You will be presented with a simple form for adding customers to a database.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
    mvn dependency:sources
-    mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/dist/README.html b/dist/README.html deleted file mode 100644 index 6b9a22a382..0000000000 --- a/dist/README.html +++ /dev/null @@ -1,47 +0,0 @@ -

Distribution

-

This is a Maven assembly to create a zip distro of the quickstarts. To run

-
mvn clean install
-
-

You will find a zip in target/jboss-as-docs-<version>.zip

-

The README.md in src/main/assembly will be included in the finished zip.

-

Release process for quickstarts

-
    -
  1. Release the archetypes
    2. -
  2. -

    Regenerate the archetype based quickstarts

    -
    ./release-utils.sh -r <version of archetypes>
-
    -
    3. -
-

This script assumes that the archetypes and quickstarts are version sync'd -3. Commit any changes to the archetype based quickstarts -4. Update versions by running

-
    ./release-utils.sh -u -o <old snapshot version> -n <release version>
-
-
    -
  1. Commit the version update
    2. -
  2. -

    Tag

    -
    git tag -a <release version> -m "Release <release version"
-
    -
    3. -
  3. -

    Reset version numbers to snapshots

    -
    ./release-utils.sh -u -o <release version> -n <new snapshot version>
-
    -
    4. -
  4. -

    Checkout the tag

    -
    git checkout <release version>
-
    -
      -
    1. -

      Build the dist

      -

      mvn clean install -10. Upload the dist to http://download.jboss.org

      -

      rsync -Pv target/jboss-as-docs-.zip jbossas@filemgmt.jboss.org:downloads_htdocs/jbossas/7.// -11. Update jboss.org/jbossas/downloads

      -
      2. -
    -
    5. -
\ No newline at end of file diff --git a/dist/src/main/assembly/README.html b/dist/src/main/assembly/README.html deleted file mode 100644 index c66e3b25aa..0000000000 --- a/dist/src/main/assembly/README.html +++ /dev/null @@ -1,43 +0,0 @@ -

JBoss AS Quickstarts

-

These are the quickstarts JBoss AS 7. You will find detailed tutorials in the -various guides at. -https://docs.jboss.org/author/display/AS7

-

The Getting Started Developing Applications Guide - -https://docs.jboss.org/author/display/AS7/Getting+Started+Developing+Applications+Guide -contains tutorials for:

- \ No newline at end of file diff --git a/ejb-in-ear/README.html b/ejb-in-ear/README.html deleted file mode 100644 index 751d10fa3b..0000000000 --- a/ejb-in-ear/README.html +++ /dev/null @@ -1,74 +0,0 @@ -

ejb-in-ear: Deployment of an EAR Containing a JSF WAR and an EJB JAR

-

Author: Paul Robinson

-

What is it?

-

This example demonstrates the deployment of an EAR artifact. The EAR contains: JSF 2.0 WAR and an EJB 3.1 JAR.

-

The example is composed of three maven projects, each with a shared parent. The projects are as follows:

-
    -
  1. -

    ejb -This project contains the EJB code and can be built independently to produce the JAR archive.

    -
    2. -
  2. -

    web -This project contains the JSF pages and the managed bean.

    -
    3. -
  3. -

    ear -This project builds the EAR artifact and pulls in the ejb and web artifacts.

    -
    4. -
-

The root pom builds each of the projects in the above order and deploys the EAR archive to the server.

-

The example follows the common "Hello World" pattern. These are the steps that occur:

-
    -
  1. A JSF page asks the user for their name.
    2. -
  2. On clicking 'Greet', the name is sent to a managed bean (Greeter).
    3. -
  3. On setting the name, the Greeter invokes the GreeterEJB, which was injected to the managed bean (notice the field annotated with @EJB).
    4. -
  4. The response from invoking the GreeterEJB is stored in a field (message) of the managed bean.
    5. -
  5. The managed bean is annotated as @SessionScoped, so the same managed bean instance is used for the entire session. This ensures that the message is available when the page reloads and is -displayed to the user.
    6. -
-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy ear/target/jboss-as-ejb-in-ear.ear.

-

The application will be running at the following URL http://localhost:8080/jboss-as-ejb-in-ear.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/ejb-in-war/README.html b/ejb-in-war/README.html deleted file mode 100644 index cf9b15b339..0000000000 --- a/ejb-in-war/README.html +++ /dev/null @@ -1,59 +0,0 @@ -

ejb-in-war: Deployment of a WAR Containing an EJB

-

Author: Paul Robinson

-

What is it?

-

This example demonstrates the deployment of an EJB 3.1 bean bundled in a war archive for deployment to JBoss AS 7.

-

The example follows the common "Hello World" pattern. These are the steps that occur:

-
    -
  1. A JSF page asks the user for their name.
    2. -
  2. On clicking submit, the name is sent to a managed bean (Greeter).
    3. -
  3. On setting the name, the Greeter invokes the GreeterEJB, which was injected to the managed bean (notice the field annotated with @EJB).
    4. -
  4. The response from invoking the GreeterEJB is stored in a field (message) of the managed bean.
    5. -
  5. The managed bean is annotated as @SessionScoped, so the same managed bean instance is used for the entire session. This ensures that the message is available when the page reloads and is -displayed to the user.
    6. -
-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-ejb-in-war.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-ejb-in-war.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/ejb-remote/README.html b/ejb-remote/README.html deleted file mode 100644 index 687c96fced..0000000000 --- a/ejb-remote/README.html +++ /dev/null @@ -1,60 +0,0 @@ -

ejb-remote: Remote EJB Client Example

-

Authors: Jaikiran Pai and Mike Musgrove

-

What is it?

-

This example shows how to access an EJB from a remote Java client program. It -demonstrates the use of EJB 3.1 and JNDI in JBoss AS 7.

-

There are two parts to the example: a server side component and a remote client program -that accesses it. Each part is in its own standalone Maven module, however the quickstart -does provide a top level module to simplify the packaging of the artifacts.

-

The server component is comprised of a stateful and a stateless EJB. The client program looks -up the stateless and stateful beans via JNDI and invokes methods on them.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

Building and deploying the application

-

Start JBoss AS 7 (or EAP 6):

-
    $JBOSS_HOME/bin/standalone.sh
-
-

To build both the server side component and a remote client program change into the -examples quickstart directory and type:

-
    mvn clean install
-
-

The server side component is packaged as a jar and needs deploying to the AS you just started:

-
    cd server-side
-    mvn jboss-as:deploy
-
-

This maven goal will deploy server-side/target/jboss-as-ejb-remote-app.jar. You can check the AS -console to see information messages regarding the deployment.

-

Note that you can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

Now start a client that will access the beans you just deployed:

-
    cd ../client
-    mvn exec:exec
-
-

You should see output showing:

- -

To undeploy the server side component from JBoss AS:

-
    cd ../server-side
-    mvn jboss-as:undeploy
-
-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
    mvn dependency:sources
-    mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/forge-from-scratch/README.html b/forge-from-scratch/README.html deleted file mode 100644 index 2a18f733f5..0000000000 --- a/forge-from-scratch/README.html +++ /dev/null @@ -1,87 +0,0 @@ -

forge-from-scratch: Example Showing How Forge Can Generate an Application From Scratch

-

Author: Lincoln Baxter

-

What is it?

-

This is an example of creating a fully Java EE compliant project using nothing -but JBoss Forge. Once generated, the sample project will be a standard Maven 3 -Java Web project with JPA 2.0, EJB 3.1, CDI 1.0, JSF 2.0 views for creating, reading, updating -and deleting records, and complete JAX-RS endpoints for all data Entities.

-

But that is not all! You can use Forge on your new or existing projects -to continue enhancing any application.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, and an installation -of JBoss Forge version 1.0.0.Beta5 or higher.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

With the prerequisites out of the way, you are ready to build and deploy. Note that you -do not need Maven installed in order to build this application because Forge bundles -an embedded Maven 3 installation.

-

Generating, Building, and Deploying the application

-

First, you need to install JBoss Forge version 1.0.0.Beta5 or higher. Follow the instructions at:

-

Installing Forge

-

Then, you need to run $ forge from the command line, or from within JBoss Tools -or by pressing CTRL-4.

-

Change to the directory where this README.md file is located, using the cd command.

-
 forge> cd /path/to/quickstart/forge-from-scratch/
-
-

Notice that there is a file called generate.fsh in this directory; run from Forge -using the run command:

-
 forge> run generate.fsh
-
-

This command will prompt you for the {project-name} (E.g: 'example'), -and will also prompt for the top level package. This should be the domain for your -organization. (E.g: 'com.example')

-

What did we create?

-

This quickstart has set up a native Java EE 6 application. After this command completes, look in your -QUICKSTART_HOME/forge-from-scratch/ folder. You will see a folder with the same name as the project-name -you entered in the prompt above. Browse through this project to see the code that was generated as a result of this command. -For a full description of what was generated by running this script and details on the structure of the application, -visit the Forge UI Scaffolding Guide

-

Deploy and test the newly generated application

-

Next, you need to start JBoss AS 7 (or EAP 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To build the application, type 'build', then to deploy the application, use the -'jboss-as-7' Forge plugin; just type:

-
 forge> forge install-plugin jboss-as-7
- forge> as7 setup
- forge> as7 deploy
-
-

This will deploy target/{project-name}.war.

-

The application will be running at the following URL http://localhost:8080/{project-name}/. -You may access it at this URL, just make sure to replace {project-name} with the name of the -project you chose when running the script.

-

To undeploy from JBoss AS, run this command:

-
 forge> as7 undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Next Steps

-

Open generate.fsh and take a look inside! There is not much magic happening here. All of the -commands used to generate this project are clearly listed just as if they were typed by your -own hands.

-

Play around with creating more entities, relationships, UI, and generating JAX-RS endpoints, -all with just a few simple commands.

-

Explore plugins!

-

Forge has a rich plugin ecosystem. Want to deploy your application to the Cloud? -Use the Forge Openshift Express plugin: http://github.com/forge/plugin-openshift-express/

-

To see a full list of avaialable plugins, make sure that you have an active internet connection and type:

-
 forge> forge find-plugin *
-
-

Importing the project into an IDE

-

If you created the project using the Forge Console in JBoss Tools, then there is -nothing to do; the projet should already be imported.

-

If you created the project from a Forge console running outside of the IDE, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
forge> mvn dependency:sources
-forge> mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/greeter/README.html b/greeter/README.html deleted file mode 100644 index 1bda8e0dd5..0000000000 --- a/greeter/README.html +++ /dev/null @@ -1,17 +0,0 @@ -

greeter: Greeter Example

-

Author: Pete Muir

-

What is it?

-

This example demonstrates the use of CDI 1.0, JPA 2.0, JTA 1.1, EJB 3.1 and JSF 2.0 in -JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

System requirements

-

The example can be deployed using Maven from the command line or from Eclipse using -JBoss Tools.

-

To set up Maven or JBoss Tools in Eclipse, refer to the -Getting Started Developing Applications Guide.

-

Deploying the application

-

To deploy the application to JBoss AS 7 (or JBoss Enterprise Application Platform 6) using Maven, start the JBoss application server and type

-
mvn package jboss-as:deploy
-
-

The application is deployed to http://localhost:8080/jboss-as-greeter.

-

You can read more details in the -Getting Started Developing Applications Guide.

\ No newline at end of file diff --git a/h2-console/README.html b/h2-console/README.html deleted file mode 100644 index 946b714d83..0000000000 --- a/h2-console/README.html +++ /dev/null @@ -1,54 +0,0 @@ -

h2-console: Example Using the H2 Console with JBoss

-

Author: Pete Muir

-

What is it?

-

JBoss AS bundles H2 as an in memory, in process database. H2 is written in Java so -can run on any platform JBoss AS runs.

-

This is quickstart shows you how to use the H2 console with JBoss AS. It reuses the -jboss-as-greeter quickstart as a GUI for entering data.

-

System requirements

-

All you need to follow these instructions is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better, and the jboss-as-greeter quickstart (normally located in ../greeter).

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

Note: Unlike most of the quickstarts, you will require JBoss AS 7.1.x or later to use this quickstart.

-

Finally, you'll need the H2 Console. You can download it from http://www.h2database.com/html/download.html. We recommend using the platform independent zip.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the sample jboss-as-greeter application

-

First you need to start JBoss AS 7 (or EAP 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal. Assuming the jboss-as-greeter application is in ../greeter:

-
mvn package -f ../greeter/pom.xml
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy -f ../greeter/pom.xml
-
-

This will deploy target/jboss-as-greeter.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-greeter/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy -f ../greeter/pom.xml
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

You can read more about the greeter application in the README.md for that project.

-

Deploying the H2 Console

-

This quickstart comes bundled with a version of the H2 Console built for JBoss AS 7 (the changes to -the stock console are discussed below). Deploy the console by copying the h2console.war to the $JBOSS_HOME/standalone/deployments directory. You can use the console by visiting http://localhost:8080/h2console.

-

You need to enter the JDBC URL, and credentials. To access the "test" database that the greeter quickstart uses, use these details

- -

Now, hit the Test Connection button, and make sure you can connect. If you can, go ahead and click Connect.

-

Now, let's take a look at the data added by the greeter application. Run the following SQL command

-
select * from users;
-
-

You should see the two seed users, and any you have added using the greeter application

-

Changes to the H2 Console for JBoss AS 7

-

In order to make the H2 console run on JBoss AS 7 we had to add a dependency on the H2 module from JBoss AS (added to the META-INF/MANIFEST.MF), and remove the H2 libraries from the war. The rebuilt console is provided in this quickstart.

\ No newline at end of file diff --git a/helloworld-gwt/README.html b/helloworld-gwt/README.html deleted file mode 100644 index d2f22d5201..0000000000 --- a/helloworld-gwt/README.html +++ /dev/null @@ -1,44 +0,0 @@ -

helloworld-gwt: Helloworld with a GWT (Google Web Toolkit) Front End Client

-

Author: Christian Sadilek

-

What is it?

-

This example demonstrates the use of CDI 1.0 and JAX-RS in JBoss AS 7 or JBoss Enterprise Application Platform 6 with a GWT front-end client. -GWT is basically a typesafe, statically checked programming model for producing HTML5+CSS3+JavaScript -front-ends. In this example, we use RESTful services on the backend.

-

You can test the REST endpoint at the URL http://localhost:8080/jboss-as-helloworld-gwt/hello/json/David

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7.

-

NOTE: -This project retrieves artifacts from the JBoss Community Maven repository, a -superset of the Maven central repository.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the Application

-

First you need to start JBoss AS 7 or JBoss Enterprise Application Platform 6. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn clean package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-helloworld-gwt.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-helloworld-gwt/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

-

Running the Application in GWT Dev Mode

-

GWT Dev Mode provides an edit-save-refresh development experience. If you plan to try -modifying this demo, we recommend you start the application in Dev Mode so you don't -have to repackage the whole application every time you change it.

-

Deploy the war file and start JBoss AS 7 as described above.

-

Then execute the command:

-
mvn gwt:run
-
\ No newline at end of file diff --git a/helloworld-html5/README.html b/helloworld-html5/README.html deleted file mode 100644 index a6b48d56f7..0000000000 --- a/helloworld-html5/README.html +++ /dev/null @@ -1,12 +0,0 @@ -

POH5 Hello World Example

-

This example demonstrates the use of CDI 1.0 and JAX-RS in JBoss AS 7 using the POH5 architecture. -POH5 is basically a smart, HTML5+CSS3+JavaScript front-end using RESTful services on the backend.

-

The example can be deployed using Maven from the command line or from Eclipse using JBoss Tools.

-

To set up Maven or JBoss Tools in Eclipse, refer to the Getting Started Guide.

-

To deploy to JBoss AS 7, start JBoss AS 7, and type mvn package jboss-as:deploy.

-

The application is deployed to http://localhost:8080/poh5-helloworld

-

You can test the REST endpoint using the following URL -http://localhost:8080/poh5-helloworld/hello/json/David

-

HelloWorld.java - establishes the RESTful endpoints using JAX-RS

-

Web.xml - maps RESTful endpoints to "/hello"

-

index.html - is a jQuery augmented plain old HTML5 web page

\ No newline at end of file diff --git a/helloworld-jms/README.html b/helloworld-jms/README.html deleted file mode 100644 index 3bdaa7c51c..0000000000 --- a/helloworld-jms/README.html +++ /dev/null @@ -1,53 +0,0 @@ -

HelloWorld JMS Example

-

This example demonstrates the use of external JMS clients with JBoss AS 7.

-

The example provides a demonstration of both producing and consuming messages to and from -a JMS destination deployed in the JBoss AS 7 environment. The example can be run from the Maven -commandline, or from the Eclipse environment.

-

To run the example from the commandline simply type:

-
mvn compile exec:java
-
-

The example provides for a certain amount of customization for the mvn:exec plugin via system properties explained below:

-

Required Properties

- -

Which connection type to the JMS provider you want to use. Accepted values are netty or jndi.

-

Default: netty

-

Note: Currently external JNDI access is under development in JBoss AS 7. As a result netty is the default value.

- -

The JNDI initial context factory you wish to use

-

Default: org.jboss.as.naming.InitialContextFactory

- -

The provider URL of the JNDI context you wish to use

-

Default: jnp://localhost:1099

-

Optional Properties

- -

The JNDI name of the JMS ConnectionFactory you want to use.

-

Default: RemoteConnectionFactory

- -

The JNDI name of the JMS Destination you want to use.

-

Default: testQueue

- -

The content of the JMS TextMessage.

-

Default: "Hello, World!"

- -

The number of JMS messages you want to produce and consume.

-

Default: 1

-

Deployment Note

-

By default, the JMS messaging provider is not deployed with the standalone JBoss AS 7 server. You will either need to run -a domain server, or configure the standalone server for JMS message. Please refer to the JBoss AS 7 Documentation for further details.

-

To run the standalone server with JMS Messaging enabled

-
standalone.sh -c standalone-full.xml
-
\ No newline at end of file diff --git a/helloworld-jsf/README.html b/helloworld-jsf/README.html deleted file mode 100644 index f5956293f0..0000000000 --- a/helloworld-jsf/README.html +++ /dev/null @@ -1,46 +0,0 @@ -

helloworld-jsf: Helloworld with a JSF (JavaServer Faces) Front End

-

Author: Brian Leathem

-

What is it?

-

This is your project! It's a sample, deployable Maven 3 project to help you -get your foot in the door developing with Java EE 6 on JBoss AS 7 or EAP 6. This -project is setup to allow you to create a compliant Java EE 6 application -using JSF 2.0, CDI 1.0, and RichFaces 4.1. In the example, a standard JSF -h:inputText component is ajax enabled using the RichFaces a4j:ajax tag, -triggering the application server to re-render a sub-section of the page on -a browser event.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or EAP 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-helloworld-jsf.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-helloworld-jsf/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/helloworld-mdb/README.html b/helloworld-mdb/README.html deleted file mode 100644 index ecf38979af..0000000000 --- a/helloworld-mdb/README.html +++ /dev/null @@ -1,46 +0,0 @@ -

helloworld-mdb: Helloword Using an MDB (Message-Driven Bean)

-

Author: Serge Pagop

-

What is it?

-

This example demonstrates the use of JMS 1.1 and EJB 3.1 Message-Driven Bean in JBoss AS 7.1.0.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

NOTE: -This Project will use the already default configured connection factory named "InVmConnectionFactory" with the jndi "java:/ConnectionFactory" and a queue named "testQueue" with the jndi "queue/test". -The artifacts will come from the JBoss Community Maven repository, a superset of the Maven central repository.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

Instructions for starting the server vary slightly depending upon whether you are using -the community release (JBoss AS 7) or the platform release (JBoss Enterprise Application Platform 6).

-

For JBoss AS 7:

-
On Linux run: $JBOSS_HOME/bin/standalone.sh -c standalone-full.xml
-
-On Windows run: $JBOSS_HOME/bin/standalone.bat -c standalone-full.xml
-
-

For JBoss Enterprise Application Platform 6:

-
On Linux run: $JBOSS_HOME/bin/standalone.sh
-
-On Windows run: $JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-helloworld-mdb.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-helloworld-mdb/HelloWorldMDBServletClient.

-

Go to the JBoss Application Server console or Server log and the result can look like this:

-

15:42:35,453 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldMDB] (Thread-47 (group:HornetQ-client-global-threads-1267410030)) Received Message: This is message 1 -15:42:35,455 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldMDB] (Thread-46 (group:HornetQ-client-global-threads-1267410030)) Received Message: This is message 2 -15:42:35,457 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldMDB] (Thread-50 (group:HornetQ-client-global-threads-1267410030)) Received Message: This is message 3 -15:42:35,478 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldMDB] (Thread-53 (group:HornetQ-client-global-threads-1267410030)) Received Message: This is message 5 -15:42:35,481 INFO [class org.jboss.as.quickstarts.mdb.HelloWorldMDB] (Thread-52 (group:HornetQ-client-global-threads-1267410030)) Received Message: This is message 4

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

\ No newline at end of file diff --git a/helloworld-osgi/README.html b/helloworld-osgi/README.html deleted file mode 100644 index ca4a57ffae..0000000000 --- a/helloworld-osgi/README.html +++ /dev/null @@ -1,18 +0,0 @@ -

helloworld-osgi: Helloworld Using OSGi (Open Services Gateway initiative)

-

Author: Pete Muir

-

What is it?

-

This example demonstrates the use of OSGi in JBoss AS 7.

-

System requirements

-

The example can be deployed using Maven from the command line, by using the AS 7 -web console or by dropping the OSGi bundle in the deployments folder.

-

To set up Maven or JBoss Tools in Eclipse, refer to the -Getting Started Developing Applications Guide.

-

Deploying the application

-

To deploy to the application to JBoss AS 7 using Maven, start JBoss AS 7 and type:

-
mvn package jboss-as:deploy
-
-

This will build, deploy and start the OSGi bundle. You will see a - Hello AS7 World!! -message appear on the console when this is done.

-

You can read more details in the -Getting Started Developing Applications Guide.

\ No newline at end of file diff --git a/helloworld-rs/README.html b/helloworld-rs/README.html deleted file mode 100644 index 5459902f3f..0000000000 --- a/helloworld-rs/README.html +++ /dev/null @@ -1,17 +0,0 @@ -

helloworld-rs: Helloworld Using JAX-RS (Java API for RESTful Web Services)

-

Authors: Gustavo A. Brey and Gaston Coco

-

What is it?

-

This example demonstrates the use of CDI 1.0 and JAX-RS in JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

System requirements

-

The example can be deployed using Maven from the command line or from Eclipse using JBoss Tools.

-

To set up Maven or JBoss Tools in Eclipse, refer to the -Getting Started Developing Applications Guide.

-

Deploying the application

-

To deploy to JBoss AS 7 or JBoss Enterprise Application Platform 6, start the JBoss application server and type:

-
mvn package jboss-as:deploy
-
-

The application is deployed to http://localhost:8080/jboss-as-helloworld-rs, so in order to get either both content you will have to point

- \ No newline at end of file diff --git a/helloworld-singleton/README.html b/helloworld-singleton/README.html deleted file mode 100644 index 295d47fab5..0000000000 --- a/helloworld-singleton/README.html +++ /dev/null @@ -1,32 +0,0 @@ -

helloworld-singleton: Helloworld Using a Singleton EJB

-

Author: Serge Pagop

-

What is it?

-

This quickstart demonstrates the use of an EJB 3.1 Singleton Bean in JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to enable the "admin" user from $JBOSS_HOME/standalone/configuration/mgmt-users.properties file, and then start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run this script

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-helloworld-singleton.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-helloworld-singleton.

-

This example demonstrates a singleton session bean that maintains state information for 2 variables: "Increment A" and "Increment B". A counter is incremented when you click on the link to the variable name. If you close and restart your browser, or if you have multiple browsers, you can see that the counter always increments the last value. These values are maintained until you restart the server. To test the singleton bean, on the home page, click on either "Increment A" or "Increment B". The result page will give you the current value of the variable.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

\ No newline at end of file diff --git a/helloworld/README.html b/helloworld/README.html deleted file mode 100644 index 704b73880d..0000000000 --- a/helloworld/README.html +++ /dev/null @@ -1,16 +0,0 @@ -

helloworld: Helloworld Example

-

Author: Pete Muir

-

What is it?

-

This example demonstrates the use of CDI 1.0 and Servlet 3 in JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

System requirements

-

The example can be deployed using Maven from the command line or from Eclipse using -JBoss Tools.

-

To set up Maven or JBoss Tools in Eclipse, refer to the -Getting Started Developing Applications Guide.

-

Deploying the application

-

To deploy the application to JBoss AS 7 (or JBoss Enterprise Application Platform 6) using Maven, start the JBoss application server and type

-
mvn package jboss-as:deploy
-
-

The application is deployed to http://localhost:8080/jboss-as-helloworld.

-

You can read more details in the -Getting Started Developing Applications Guide.

\ No newline at end of file diff --git a/hibernate3/README.html b/hibernate3/README.html deleted file mode 100644 index b3bc87e9a7..0000000000 --- a/hibernate3/README.html +++ /dev/null @@ -1,44 +0,0 @@ -

hibernate3: How to Use Hibernate 3 in an Application

-

Author: Bartosz Baranowski

-

What is it?

-

This is a simple JSF 2.0 example based on hibernate4 quickstart. Its purpose is to demonstrate how you can use Hibernate 3 in your application.

-

This quickstart, like the log4j quickstart, demonstrates how to define a module dependency. However, this quickstart goes beyond that and also demonstrates the following:

-
* WAR creation - The Maven script and Maven WAR plugin create a *WAR* archive that includes ONLY the Hibernate 3.x binaries. To understand better how this is achieved, please refer to the *pom.xml* in the root directory of this quickstart. Additional information can be found in the <http://maven.apache.org/plugins/maven-war-plugin> documentation.
-* Module exclusion and inclusion - This example demonstrates how to control class loading using *dependencies* and *exclusions* in the *jboss-deployment-structure.xml* file. For more information about this file, please refer to <https://docs.jboss.org/author/display/AS7/Developer+Guide#DeveloperGuide-JBossDeploymentStructureFile>
-* Persistence configuration - Configuration is required to tell the container how to load JPA/Hibernate.
-
-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-hibernate3.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-hibernate3/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/hibernate4/README.html b/hibernate4/README.html deleted file mode 100644 index b9ac7df5ef..0000000000 --- a/hibernate4/README.html +++ /dev/null @@ -1,78 +0,0 @@ -

hibernate4: How to Use Hibernate 4 in an Application

-

Author: Madhumita Sadhukhan

-

What is it?

-

This is a quickstart built upon kitchensink additionally demonstrating how to use Hibernate4 as ORM over JPA in AS7(or EAP6)! -It's a sample, deployable Maven 3 project to help you -get your foot in the door developing with Java EE 6 and Hibernate 4 on JBoss AS 7 or EAP 6. This -project is setup to allow you to create a compliant Java EE 6 application -using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 , Hibernate-Core and Hibernate Bean Validation. -It includes a persistence unit associated with Hibernate session and some sample persistence and transaction code -to help you get your feet wet with database access in enterprise Java.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Adding correct Dependencies

-

JBoss AS7 (or EAP 6) provides both JPA as well as Hibernate4(as ORM) and also supports Hibernate3 etc. -If you choose to use Hibernate4 packaged within JBoss AS7(or EAP6) you will need to first import the JPA API. -This quickstart demonstrates usage of Hibernate Session and Hibernate Validators. -You will also need to add dependencies to the required Hibernate modules for using these features in pom.xml with scope as provided. -for eg .

-
  <dependency>
-     <groupId>org.hibernate</groupId>
-     <artifactId>hibernate-validator</artifactId>
-     <version>4.2.0.Final</version>
-     <scope>provided</scope>
-     <exclusions>
-        <exclusion>
-           <groupId>org.slf4j</groupId>
-           <artifactId>slf4j-api</artifactId>
-        </exclusion>
-     </exclusions>
-  </dependency>
-
-

You may refer "Adding a new external dependency" located at http://community.jboss.org/wiki/HackingOnAS7 for further help on adding dependencies.

-

Please note that if you are working with Hibernate 3 the process is different as you will need to bundle the jars since JBoss AS7(or EAP6) -does not ship with Hibernate 3. -Please refer to the quickstart demonstrating Hibernate3 for details on how to bundle the jars in such cases.

-

Deploying the application

-

First you need to start JBoss AS 7 (or EAP 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-hibernate4.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-hibernate4/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Guide for Developers.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/jts/README.html b/jts/README.html deleted file mode 100644 index 094b2ac20a..0000000000 --- a/jts/README.html +++ /dev/null @@ -1,95 +0,0 @@ -

jts (Java Transaction Service): Distributed EJB Transactions Across Multiple Containers

-

Author: Tom Jenkinson

-

What is it?

-

This example demonstrates how to perform distributed transactions in an application. A -distributed transaction is a set of operations performed by two or more nodes -participating in an activity coordinated as a single entity of work and fulfilling -the properties of an ACID transaction. ACID meaning:

- -

The example uses Java Transaction Service (JTS) to propagate a transaction context across -two Container-Managed Transaction (CMT) EJBs that, although deployed in separate servers, -participate in the same transaction. In this example, one server processes the -Customer and Account data and the other server processes the Invoice data.

-

The example expects the EJBs to be deployed onto the same physical machine. This is not a -restriction of JTS and the example can easily be converted to run on separate machines by -editing the hostname value for the InvoiceManagerEJB in org.jboss.as.quickstarts.cmt.jts.ejb.AccountManagerEJB.

-

The example builds upon the CMT example also available in the quickstarts.

-

Again, a simple MDB has been provided that prints out the messages sent but this is not a -transactional MDB and is purely provided for debugging purposes.

-

You will see that the AccountManagerEJB uses the EJB home for the remote EJB, this is expected -to connect to remote EJBs and could be simplified if the EJB was deployed locally.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

Testing the application

-

NOTE: Due to a difference in configuration between JBoss AS 7 and JBoss Enterprise Application Platform 6, all references of standalone-full.xml -apply to JBoss AS 7 only, you can replace these references with standalone.xml if deploying into JBoss Enterprise Application Platform 6.

-

For this example, you will need two instances of the application server, with a subtle startup -configuration difference. Application server 2 must be started up with a port offset provided -to the startup script as "-Djboss.socket.binding.port-offset=100"

-

The application servers 1 should both be configured as follows:

-
    -
  1. Open the file /standalone/configuration/standalone-full.xml
    2. -
  2. Enable JTS: - Find the orb subsystem and change the configuration to: - - - - - - Find the transaction subsystem and append the element: - - - -
    3. -
-

To start JBoss AS 7 (or JBoss Enterprise Application Platform 6) with a JMS connection factory and a queue named test queue in it. The instructions -for this vary slightly depending upon whether you are using the community release (JBoss AS 7) or the platform release (JBoss Enterprise Application Platform 6)

-

For JBoss AS 7:

-
    <APP_SERVER_1_HOME>/bin/standalone.sh -c standalone-full.xml
-    <APP_SERVER_2_HOME>/bin/standalone.sh -c standalone-full.xml -Djboss.socket.binding.port-offset=100
-
-

or if you are using windows

-
    <APP_SERVER_1_HOME>\bin\standalone.bat -c standalone-full.xml
-    <APP_SERVER_2_HOME>\bin\standalone.bat -c standalone-full.xml -Djboss.socket.binding.port-offset=100
-
-

For JBoss Enterprise Application Platform 6:

-
    <APP_SERVER_1_HOME>/bin/standalone.sh
-    <APP_SERVER_2_HOME>/bin/standalone.sh -Djboss.socket.binding.port-offset=100
-
-

or if you are using windows

-
    <APP_SERVER_1_HOME>\bin\standalone.bat
-    <APP_SERVER_2_HOME>\bin\standalone.bat -Djboss.socket.binding.port-offset=100
-
-

To deploy the application, you first need to produce the archives to deploy using -the following Maven goals. Note that application-component-2 must be built first as it provides an EJB client -to application-component-1. Also note that application-component-2 must be "installed"

-
    cd <JTS_QUICKSTART_HOME>/application-component-2
-    mvn install
-    cd <JTS_QUICKSTART_HOME>/application-component-1
-    mvn package
-
-

You can now deploy the artifact to the JBoss application server by executing the following command. Again, due to the way the -application is written (with little failure detection), it is best to deploy application-component-2 first -so that when application-component-1 is deployed it can resolve the EJB from the other container:

-
    cd <JTS_QUICKSTART_HOME>/application-component-2
-    mvn jboss-as:deploy
-    cd <JTS_QUICKSTART_HOME>/application-component-1
-    mvn jboss-as:deploy
-
-

The application will now be running at the following URL http://localhost:8080/jboss-as-jts-application-component-1/.

-

When you enter a name and click to "invoice" that customer, you will see the following in the application server 1 console: -12:09:38,424 INFO [org.jboss.ejb.client] (http-localhost-127.0.0.1-8080-1) JBoss EJB Client version 1.0.0.Beta11 -12:09:38,513 ERROR [jacorb.orb] (http-localhost-127.0.0.1-8080-1) no adapter activator exists for jboss-as-jts-application-component-2&%InvoiceManagerEJBImpl&%home -12:09:39,204 INFO [class org.jboss.as.quickstarts.cmt.jts.mdb.HelloWorldMDB] (Thread-1 (group:HornetQ-client-global-threads-1095034080)) Received Message: Created customer named: Tom

-

You will also see the following in application-server-2 console: -12:09:38,697 INFO [org.jboss.ejb.client] (RequestProcessor-10) JBoss EJB Client version 1.0.0.Beta11 -12:09:39,204 INFO [class org.jboss.as.quickstarts.cmt.jts.mdb.HelloWorldMDB] (Thread-3 (group:HornetQ-client-global-threads-649946595)) Received Message: Created invoice for customer named: Tom

-

The web page will change with a prompt for you to check the logs for the MDB messages in the server consoles above at which point you can be satisfied that the quickstart -has operated correctly.

\ No newline at end of file diff --git a/kitchensink-ear/README.html b/kitchensink-ear/README.html deleted file mode 100644 index 438f9b5089..0000000000 --- a/kitchensink-ear/README.html +++ /dev/null @@ -1,63 +0,0 @@ -

kitchensink-ear: Example Using Multiple Java EE 6 Technologies Deployed as an EAR

-

Author: Pete Muir

-

What is it?

-

This is your project! It's a sample, deployable Maven 3 project to help you -get your foot in the door developing with Java EE 6 on JBoss AS 7 or JBoss Enterprise Application Platform 6. This -project is setup to allow you to create a compliant Java EE 6 application -using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes -a persistence unit and some sample persistence and transaction code to help -you get your feet wet with database access in enterprise Java.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss A. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

S -To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-kitchensink-ear.ear.

-

The application will be running at the following URL http://localhost:8080/jboss-as-kitchensink-ear/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

-

Running the Arquillian tests

-

By default, tests are configured to be skipped. The reason is that the sample -test is an Arquillian test, which requires the use of a container. You can -activate this test by selecting one of the container configuration provided -for JBoss AS 7 (remote).

-

To run the test in JBoss AS 7, first start a JBoss AS 7 instance. Then, run the -test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-remote
-
-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/kitchensink-html5-mobile/README.html b/kitchensink-html5-mobile/README.html deleted file mode 100644 index 886ce1095a..0000000000 --- a/kitchensink-html5-mobile/README.html +++ /dev/null @@ -1,93 +0,0 @@ -

html5-mobile: Mobile Example Using Plain Old HTML5 (POH5)

-

Author: Jay Balunas

-

What is it?

-

This is your project! It's a deployable Maven 3 project to help you -get your foot in the door developing HTML5 based desktop/mobile web applications with Java EE 6 -on JBoss. This project is setup to allow you to create a basic Java EE 6 application -using HTML5, jQuery Mobile, JAX-RS, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes -a persistence unit and some sample persistence and transaction code to help -you get your feet wet with database access in enterprise Java.

-

This application is built using a technique called Plain Old HTML5 (POH5). This uses a pure HTML -client that interacts with with the application server via restful end-points (JAX-RS). This -application also uses some of the latest HTML5 features and advanced JAX-RS. And since testing -is just as important with POH5 as it is server side core this application also uses QUnit to show -you how to unit test your JavaScript.

-

What is a modern web application without mobile web support? This application also integrates -jQuery mobile and basic client side device detection to give you both a desktop and mobile -version of the interface. Both support the same features, including form validation, member -registration, etc. However the mobile version adds in mobile layout, touch, and performance -improvements needed to get you started with mobile web development on JBoss.
-

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

An HTML5 compatible browser such as Chrome 14+, Safari 5+, Firefox 5+, or IE 9+ are -required. and note that some behaviors will vary slightly (ex. validations) based on browser support, -especially IE 9.

-

Mobile web support is limited to Android and iOS devices. It should run on HP, -and Black Berry devices as well. Windows Phone, and others will be supported as -jQuery Mobile announces support.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start the JBoss container. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

Note: Adding "-b 0.0.0.0" to the above commands will allow external clients (phones, tablets, -desktops, etc...) connect through your local network.

-

For example

-
$JBOSS_HOME/bin/standalone.sh -b 0.0.0.0
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-html5-mobile.

-

The application will be running at the following URL http://localhost:8080/jboss-as-html5-mobile/.

-

To undeploy run this command:

-
mvn jboss-as:undeploy
-
-

You can also start the JBoss container and deploy the project using JBoss Tools. See the -Getting Started Developing Applications Guide -for more information.

-

Running the Arquillian tests

-

By default, tests are configured to be skipped. The reason is that the sample -test is an Arquillian test, which requires the use of a container. You can -activate this test by selecting one of the container configuration provided -for JBoss.

-

To run the test in JBoss, first start the container instance. Then, run the -test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-remote
-
-

Running the QUnit tests

-

QUnit is a JavaScript unit testing framework used and built by jQuery.This -application include a set of QUnit tests in order to verify JavaScript that -is core to this HTML5 application. Executing QUnit test cases is quite easy. -Simply load the following HTML is a browser.

-
<app-root>/src/test/qunit/index.html
-
-

For more information on QUnit tests see http://docs.jquery.com/QUnit

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse / JBoss Tools with are provided in the -Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/kitchensink-jsp/README.html b/kitchensink-jsp/README.html deleted file mode 100644 index 704c96d003..0000000000 --- a/kitchensink-jsp/README.html +++ /dev/null @@ -1,68 +0,0 @@ -

kitchensink-jsp: Example Using Multiple Java EE 6 Technologies with a JSP (JavaServer Pages) Front End

-

Author: Elvadas Nono

-

What is it?

-

jboss-as-kitchensink-jsp is a deployable Maven 3 project to help you -get your foot in the door developing with Java EE 6 on JBoss AS 7 or JBoss Enterprise Application Platform 6. This -project is setup to allow you to create a compliant Java EE 6 application -using JSP 2.0 EL 2.0 JSTL 1.2 CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0.

-

This project rebuilds the presentation tier of the kitchensink quickstart app - using JSP and JSTL instead of JSF features.

-

It is another app based on JSP that reused all other components from the -Member Registration template. -It reused the persistence unit and some sample persistence and transaction code to help -you get your feet wet with database access in enterprise Java.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-kitchensink-jsp.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-kitchensink-jsp/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

Running the Arquillian tests

-

By default, tests are configured to be skipped. The reason is that the sample -test is an Arquillian test, which requires the use of a container. You can -activate this test by selecting one of the container configuration provided -for JBoss AS 7 (remote).

-

To run the test in JBoss AS 7, first start a JBoss AS 7 instance. Then, run the -test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-remote
-
-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/kitchensink/README.html b/kitchensink/README.html deleted file mode 100644 index a376501fc6..0000000000 --- a/kitchensink/README.html +++ /dev/null @@ -1,63 +0,0 @@ -

kitchensink: Example Using Multiple Java EE 6 Technologies Deployed as a WAR

-

Author: Pete Muir

-

What is it?

-

This is your project! It's a sample, deployable Maven 3 project to help you -get your foot in the door developing with Java EE 6 on JBoss AS 7 or JBoss Enterprise Application Platform 6. This -project is setup to allow you to create a compliant Java EE 6 application -using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes -a persistence unit and some sample persistence and transaction code to help -you get your feet wet with database access in enterprise Java.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-kitchensink.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-kitchensink/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide for more information.

-

Running the Arquillian tests

-

By default, tests are configured to be skipped. The reason is that the sample -test is an Arquillian test, which requires the use of a container. You can -activate this test by selecting one of the container configuration provided -for JBoss AS 7 (remote).

-

To run the test in JBoss AS 7, first start a JBoss AS 7 instance. Then, run the -test goal with the following profile activated:

-
mvn clean test -Parq-jbossas-remote
-
-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Developing Applications Guide.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/log4j/README.html b/log4j/README.html deleted file mode 100644 index e06f8afdbe..0000000000 --- a/log4j/README.html +++ /dev/null @@ -1,56 +0,0 @@ -

log4j: How to Define a Module Dependency and Use log4j in an Application

-

Author: Bartosz Baranowski

-

What is it?

-

This simple JSF 2.0 application shows how to use container defined modules -to limit the size of the application package. It also shows how to use -common versions of certain classes at runtime.

-

Applications must often depend on third party libraries. -By default, Java EE packages allow you to include dependencies in a deployable unit -which can lead to uncontrolled growth of the deployable unit. This can be avoided by -the use of a container defined module. A modules is nothing more than a container -managed binary dependency, which is shared by all deployed applications.

-

For more details on class loading and modules please refer to -Class Loading in AS7
-

-

This example is very simple. It declares dependency on Apache Log4j module to -allow itself to use custom logging framework.This is achieved with a simple addition to the xml file: -src/main/webapp/WEB-INF/jboss-deployment-structure.xml. -For more details about this file please refer to -JBoss Deployment Structure File
-

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (or JBoss Enterprise Application Platform 6). To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-log4j.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-log4j/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/numberguess/README.html b/numberguess/README.html deleted file mode 100644 index 76e3c3cb4f..0000000000 --- a/numberguess/README.html +++ /dev/null @@ -1,15 +0,0 @@ -

numberguess: Example Using CDI (Contexts and Dependency Injection) and JSF (JavaServer Faces)

-

Author: Pete Muir

-

What is it?

-

This example demonstrates the use of CDI 1.0 and JSF 2.0 in JBoss AS 7 JBoss Enterprise Application Platform 6.

-

System requirements

-

The example can be deployed using Maven from the command line or from Eclipse using -JBoss Tools.

-

To set up Maven or JBoss Tools in Eclipse, refer to the Getting Started Developing Applications Guide.

-

Deploying the application

-

To deploy to JBoss AS 7 or JBoss Enterprise Application Platform 6 using Maven, start the server, and type:

-
mvn package jboss-as:deploy
-
-

The application is deployed to http://localhost:8080/jboss-as-numberguess.

-

You can read more details in the -Getting Started Developing Applications Guide.

\ No newline at end of file diff --git a/payment-cdi-event/README.html b/payment-cdi-event/README.html deleted file mode 100644 index 414fc76247..0000000000 --- a/payment-cdi-event/README.html +++ /dev/null @@ -1,66 +0,0 @@ -

payment-cdi-event: Use CDI Events to Process Debit and Credit Operations

-

Author: Elvadas Nono

-

This quickstart demonstrates how to use CDI 1.0 Events in JBoss AS 7 or JBoss Enterprise Application Platform 6. -The JSF front-end client allows you to create both credit and debit operation events.

-

To test this quickstart, enter an amount, choose either a Credit or Debit operation, -and then click on Pay to create the event.

-

A Session scoped (@SessionScoped) payment event handler catches the operation - and produces (@Produces) a named list of all operations performed during this session. -The event is logged in the JBoss console and the event list is displayed in - a table at the bottom of the form.

-

The payment-cdi-event quickstart defines the following classes

- -

You can test the output of this quickstart at the URL http://localhost:8080/jboss-as-payment-cdi-event

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the Application

-

First you need to start JBoss AS 7. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using Windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn clean package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-payment-cdi-event.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-payment-cdi-event/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

\ No newline at end of file diff --git a/servlet-async/README.html b/servlet-async/README.html deleted file mode 100644 index 9808ceb567..0000000000 --- a/servlet-async/README.html +++ /dev/null @@ -1,39 +0,0 @@ -

servlet-async: How to Write an Asynchronous Servlet

-

Author: Christian Sadilek

-

What is it?

-

This is a sample project showing the use of asynchronous servlets.

-

It shows how to detach the execution of a resource intensive task from the request -processing thread, so the thread is free to serve other client requests. -The resource intensive tasks are executed using a dedicated thread pool and -create the client response asynchronously.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

NOTE: -If you are running JBoss AS 7 this project retrieves artifacts from the JBoss Community Maven repository, a -superset of the Maven central repository. If you are running JBoss Enterprise Application Platform 6, -follow the instructions in the README file at the root of you quickstart folder to configure a local Maven repository.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 or JBoss Enterprise Application Platform 6. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-servlet-async.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-servlet-async/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

\ No newline at end of file diff --git a/servlet-filterlistener/README.html b/servlet-filterlistener/README.html deleted file mode 100644 index 0bdade80bb..0000000000 --- a/servlet-filterlistener/README.html +++ /dev/null @@ -1,35 +0,0 @@ -

servlet-filterlistener: How to Write Servlet Filters and Listeners

-

Author: Jonathan Fuerth

-

What is it?

-

This is a sample project showing the use of servlet filters and listeners.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

NOTE: -If you are running JBoss AS 7 this project retrieves artifacts from the JBoss Community Maven repository, a -superset of the Maven central repository. If you are running JBoss Enterprise Application Platform 6, -follow the instructions in the README file at the root of you quickstart folder to configure a local Maven repository.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7. To do this, run

-
$JBOSS_HOME/bin/standalone.sh
-
-

or if you are using windows

-
$JBOSS_HOME/bin/standalone.bat
-
-

To deploy the application, you first need to produce the archive to deploy using -the following Maven goal:

-
mvn package
-
-

You can now deploy the artifact to JBoss AS by executing the following command:

-
mvn jboss-as:deploy
-
-

This will deploy target/jboss-as-servlet-filterlistener.war.

-

The application will be running at the following URL http://localhost:8080/jboss-as-servlet-filterlistener/.

-

To undeploy from JBoss AS, run this command:

-
mvn jboss-as:undeploy
-
-

You can also start JBoss AS 7 and deploy the project using Eclipse. See the JBoss AS 7 -Getting Started Developing Applications Guide -for more information.

\ No newline at end of file diff --git a/wsat-simple/README.html b/wsat-simple/README.html deleted file mode 100644 index 04c2d81864..0000000000 --- a/wsat-simple/README.html +++ /dev/null @@ -1,100 +0,0 @@ -

wsat-simple: WS-AT (WS-AtomicTransaction) - Simple

-

Author: Paul Robinson

-

What is it?

-

This example demonstrates the deployment of a WS-AT (WS-AtomicTransaction) enabled JAX-WS Web service bundled in a war -archive for deployment to JBoss AS 7.

-

The Web service is offered by a Restaurant for making bookings. The Service allows bookings to be made within an -Atomic Transaction.

-

The example demonstrates the basics of implementing a WS-AT enabled Web service. It is beyond the scope of this -quick start to demonstrate more advanced features. In particular:

-
    -
  1. The Service does not implement the required hooks to support recovery in the presence of failures.
    2. -
  2. It also does not utilize a transactional back end resource.
    3. -
  3. Only one Web service participates in the protocol. As WS-AT is a 2PC coordination protocol, it is best suited to multi-participant scenarios.
    4. -
-

For a more complete example, please see the XTS demonstrator application that ships with the JBossTS project: http://www.jboss.org/jbosstm.

-

It is also assumed tht you have an understanding of WS-AtomicTransaction. For more details, read the XTS documentation -that ships with the JBossTS project, which can be downloaded here: http://www.jboss.org/jbosstm/downloads/JBOSSTS_4_16_0_Final

-

The application consists of a single JAX-WS web service that is deployed within a war archive. It is tested with a JBoss -Arquillian enabled JUnit test.

-

When running the org.jboss.as.quickstarts.wsat.simple.ClientTest#testCommit() method, the -following steps occur:

-
    -
  1. A new Atomic Transaction (AT) is created by the client.
    2. -
  2. An operation on a WS-AT enabled Web service is invoked by the client.
    3. -
  3. The JaxWSHeaderContextProcessor in the WS Client handler chain inserts the WS-AT context into the outgoing SOAP message
    4. -
  4. When the service receives the SOAP request, it's JaxWSHeaderContextProcessor in it's handler chain inspects the WS-AT context and associates the request with this AT.
    5. -
  5. The Web service operation is invoked...
    6. -
  6. A participant is enlisted in this AT. This allows the Web Service logic to respond to protocol events, such as Commit and Rollback.
    7. -
  7. The service invokes the business logic. In this case, a booking is made with the restaurant.
    8. -
  8. The backend resource is prepared. This ensures that the Backend resource can undo or make permanent the change when told to do so by the coordinator.
    9. -
  9. The client can then decide to commit or rollback the AT. If the client decides to commit, the coordinator will begin the 2PC protocol. If the participant decides to rollback, all participants will be told to rollback.
    10. -
-

There is another test that shows what happens if the client decides to rollback the AT.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (7.1.0.CR1 or above, or EAP 6), with the XTS sub system enabled, this is enabled through an optional server configuration (standalone-xts.xml). To do this, run the following commands, from within the top-level directory of JBossAS:

-
./bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml | egrep "started|stdout"
-
-

Note, the pipe to egrep (| egrep "started|stdout") is useful to just show when the server has started and the output from these tests. For normal operation, this pipe can be removed.

-

or if you are using windows

-
./bin/standalone.bat --server-config=../../docs/examples/configs/standalone-xts.xml
-
-

To test the application run:

-
mvn clean test -Parq-jbossas-remote
-
-

The following expected output should appear. The output explains what actually went on when these tests ran.

-

Test commit:

-
14:06:28,208 INFO  [stdout] (management-handler-threads - 14) Starting 'testCommit'. This test invokes a WS within an AT. The AT is later committed, which causes the back-end resource(s) to be committed.
-14:06:28,209 INFO  [stdout] (management-handler-threads - 14) [CLIENT] Creating a new WS-AT User Transaction
-14:06:28,209 INFO  [stdout] (management-handler-threads - 14) [CLIENT] Beginning Atomic Transaction (All calls to Web services that support WS-AT wil be included in this transaction)
-14:06:28,532 INFO  [stdout] (management-handler-threads - 14) [CLIENT] invoking makeBooking() on WS
-14:06:29,168 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Restaurant service invoked to make a booking
-14:06:29,168 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Enlisting a Durable2PC participant into the AT
-14:06:29,410 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Invoking the back-end business logic
-14:06:29,410 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] makeBooking called on backend resource.
-14:06:29,411 INFO  [stdout] (management-handler-threads - 14) [CLIENT] committing Atomic Transaction (This will cause the AT to complete successfully)
-14:06:29,974 INFO  [stdout] (TaskWorker-3) [SERVICE] Prepare called on participant, about to prepare the back-end resource
-14:06:29,974 INFO  [stdout] (TaskWorker-3) [SERVICE] prepare called on backend resource.
-14:06:29,974 INFO  [stdout] (TaskWorker-3) [SERVICE] back-end resource prepared, participant votes prepared
-14:06:30,560 INFO  [stdout] (TaskWorker-3) [SERVICE] all participants voted 'prepared', so coordinator tells the participant to commit
-14:06:30,560 INFO  [stdout] (TaskWorker-3) [SERVICE] commit called on backend resource.
-
-

Test rollback:

-
14:06:31,163 INFO  [stdout] (management-handler-threads - 13) Starting 'testRollback'. This test invokes a WS within an AT. The AT is later rolled back, which causes the back-end resource(s) to be rolled back.
-14:06:31,163 INFO  [stdout] (management-handler-threads - 13) [CLIENT] Creating a new WS-AT User Transaction
-14:06:31,164 INFO  [stdout] (management-handler-threads - 13) [CLIENT] Beginning Atomic Transaction (All calls to Web services that support WS-AT wil be included in this transaction)
-14:06:31,461 INFO  [stdout] (management-handler-threads - 13) [CLIENT] invoking makeBooking() on WS
-14:06:32,094 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Restaurant service invoked to make a booking
-14:06:32,094 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Enlisting a Durable2PC participant into the AT
-14:06:32,297 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Invoking the back-end business logic
-14:06:32,322 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] makeBooking called on backend resource.
-14:06:32,324 INFO  [stdout] (management-handler-threads - 13) [CLIENT] rolling back Atomic Transaction (This will cause the AT and thus the enlisted back-end resources to rollback)
-14:06:32,818 INFO  [stdout] (TaskWorker-1) [SERVICE] one or more participants voted 'aborted' or a failure occurred, so coordinator tells the participant to rollback
-14:06:32,818 INFO  [stdout] (TaskWorker-1) [SERVICE] rollback called on backend resource.
-
-

You can also start JBoss AS 7 and run the tests within Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Guide for Developers.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/wsba-coordinator-completion-simple/README.html b/wsba-coordinator-completion-simple/README.html deleted file mode 100644 index 1a6123d8e7..0000000000 --- a/wsba-coordinator-completion-simple/README.html +++ /dev/null @@ -1,108 +0,0 @@ -

wsba-coordinator-completion-simple: Example of a WS-BA (WS Business Activity) Enabled JAX-WS Web Service

-

Author: Paul Robinson

-

What is it?

-

This example demonstrates the deployment of a WS-BA (WS Business Activity) enabled JAX-WS Web service bundled in a war -archive for deployment to JBoss AS 7 or JBoss Enterprise Application Platform 6.

-

The Web service exposes a simple 'set' collection as a service. The Service allows items to be added to the set within a -Business Activity.

-

The example demonstrates the basics of implementing a WS-BA enabled Web service. It is beyond the scope of this -quick start to demonstrate more advanced features. In particular:

-
    -
  1. The Service does not implement the required hooks to support recovery in the presence of failures.
    2. -
  2. It also does not utilize a transactional back end resource.
    3. -
  3. Only one Web service participates in the protocol. As WS-BA is a coordination protocol, it is best suited to multi-participant scenarios.
    4. -
-

For a more complete example, please see the XTS demonstrator application that ships with the JBossTS project: http://www.jboss.org/jbosstm.

-

It is also assumed that you have an understanding of WS-BusinessActivity. For more details, read the XTS documentation -that ships with the JBossTS project, which can be downloaded here: http://www.jboss.org/jbosstm/downloads/JBOSSTS_4_16_0_Final

-

The application consists of a single JAX-WS web service that is deployed within a war archive. It is tested with a JBoss -Arquillian enabled JUnit test.

-

When running the org.jboss.as.quickstarts.wsba.coordinatorcompletion.simple.ClientTest#testSuccess() method, the -following steps occur:

-
    -
  1. A new Business Activity is created by the client.
    2. -
  2. Multiple operations on a WS-BA enabled Web service is invoked by the client.
    3. -
  3. The JaxWSHeaderContextProcessor in the WS Client handler chain inserts the BA context into the outgoing SOAP messages
    4. -
  4. When the service receives a SOAP request, it's JaxWSHeaderContextProcessor in it's handler chain inspects the BA context and associates the request with this BA.
    5. -
  5. The Web service operation is invoked...
    6. -
  6. For the first request, in this BA, A participant is enlisted in this BA. This allows the Web Service logic to respond to protocol events, such as compensate and close.
    7. -
  7. The service invokes the business logic. In this case, a String value is added to the set.
    8. -
  8. The client can then make additional calls to the SetService. As the SetService participates as a CoordinatorCompletion protocol, it will continue to accept calls to 'addValueToSet' until it is told to complete by the coordinator.
    9. -
  9. The client can then decide to complete or cancel the BA. If the client decides to complete, all participants will be told to complete. Providing all participants successfully complete, the coordinator will then tell all participants to close, otherwise the completed participants will be told to compensate. If the participant decides to cancel, all participants will be told to compensate.
    10. -
-

There is another test that shows:

-

How the client can cancel a BA.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or JBoss Enterprise Application Platform 6. -The following instructions target JBoss AS 7, but they also apply to JBoss Enterprise Application Platform 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (7.1.0.CR1 or above, or JBoss Enterprise Application Platform 6), with the XTS sub system enabled, this is enabled through an optional server configuration (standalone-xts.xml). To do this, run the following commands, from within the top-level directory of JBossAS:

-
./bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml | egrep "started|stdout"
-
-

Note, the pipe to egrep (| egrep "started|stdout") is useful to just show when the server has started and the output from these tests. For normal operation, this pipe can be removed.

-

or if you are using windows

-
./bin/standalone.bat --server-config=../../docs/examples/configs/standalone-xts.xml
-
-

To test the application run:

-
mvn clean test -Parq-jbossas-remote
-
-

The following expected output should appear. The output explains what actually went on when these tests ran.

-

Test success:

-
16:24:19,191 INFO  [stdout] (management-handler-threads - 10) Starting 'testSuccess'. This test invokes a WS twice within a BA. The BA is later closes, which causes these WS calls to complete successfully.
-16:24:19,191 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Creating a new Business Activity
-16:24:19,192 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Beginning Business Activity (All calls to Web services that support WS-BA wil be included in this activity)
-16:24:19,216 INFO  [stdout] (management-handler-threads - 10) [CLIENT] invoking addValueToSet(1) on WS
-16:24:19,241 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] invoked addValueToSet('1')
-16:24:19,241 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Enlisting a participant into the BA
-16:24:19,281 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Invoking the back-end business logic
-16:24:19,283 INFO  [stdout] (management-handler-threads - 10) [CLIENT] invoking addValueToSet(2) on WS
-16:24:19,308 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] invoked addValueToSet('2')
-16:24:19,308 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Re-using the existing participant, already registered for this BA
-16:24:19,308 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Invoking the back-end business logic
-16:24:19,313 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Closing Business Activity (This will cause the BA to complete successfully)
-16:24:19,419 INFO  [stdout] (TaskWorker-3) [SERVICE] Participant.complete (This tells the participant that the BA completed, but may be compensated later)
-16:24:19,498 INFO  [stdout] (TaskWorker-3) [SERVICE] Participant.confirmCompleted('true') (This tells the participant that compensation information has been logged and that it is safe to commit any changes.)
-16:24:19,498 INFO  [stdout] (TaskWorker-3) [SERVICE] Commit the backend resource (e.g. commit any changes to databases so that they are visible to others)
-16:24:19,543 INFO  [stdout] (TaskWorker-1) [SERVICE] Participant.close (The participant knows that this BA is now finished and can throw away any temporary state)
-
-

Test cancel:

-
16:24:19,616 INFO  [stdout] (management-handler-threads - 10) Starting 'testCancel'. This test invokes a WS twice within a BA. The BA is later cancelled, which causes these WS calls to be compensated.
-16:24:19,616 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Creating a new Business Activity
-16:24:19,616 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Beginning Business Activity (All calls to Web services that support WS-BA will be included in this activity)
-16:24:19,631 INFO  [stdout] (management-handler-threads - 10) [CLIENT] invoking addValueToSet(1) on WS
-16:24:19,653 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] invoked addValueToSet('1')
-16:24:19,653 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Enlisting a participant into the BA
-16:24:19,685 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Invoking the back-end business logic
-16:24:19,688 INFO  [stdout] (management-handler-threads - 10) [CLIENT] invoking addValueToSet(2) on WS
-16:24:19,713 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] invoked addValueToSet('2')
-16:24:19,713 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Re-using the existing participant, already registered for this BA
-16:24:19,713 INFO  [stdout] (http-localhost-127.0.0.1-8080-2) [SERVICE] Invoking the back-end business logic
-16:24:19,756 INFO  [stdout] (management-handler-threads - 10) [CLIENT] Cancelling Business Activity (This will cause the work to be compensated)
-16:24:19,815 INFO  [stdout] (TaskWorker-3) [SERVICE] Participant.cancel (The participant should compensate any work done within this BA)
-16:24:19,815 INFO  [stdout] (TaskWorker-3) [SERVICE] SetParticipantBA: Carrying out compensation action
-16:24:19,815 INFO  [stdout] (TaskWorker-3) [SERVICE] Compensate the backend resource by removing '1' from the set (e.g. undo any changes to databases that were previously made visible to others)
-16:24:19,816 INFO  [stdout] (TaskWorker-3) [SERVICE] Compensate the backend resource by removing '2' from the set (e.g. undo any changes to databases that were previously made visible to others)
-
-

You can also start JBoss AS 7 and run the tests within Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Guide for Developers.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file diff --git a/wsba-participant-completion-simple/README.html b/wsba-participant-completion-simple/README.html deleted file mode 100644 index f6d15c9667..0000000000 --- a/wsba-participant-completion-simple/README.html +++ /dev/null @@ -1,103 +0,0 @@ -

wsba-participant-completion-simple: Deployment of a WS-BA (WS Business Activity) - Participant Completion

-

Author: Paul Robinson

-

What is it?

-

This example demonstrates the deployment of a WS-BA (WS Business Activity) enabled JAX-WS Web service bundled in a war -archive for deployment to JBoss AS 7.

-

The Web service exposes a simple 'set' collection as a service. The Service allows items to be added to the set within a -Business Activity.

-

The example demonstrates the basics of implementing a WS-BA enabled Web service. It is beyond the scope of this -quick start to demonstrate more advanced features. In particular

-
    -
  1. The Service does not implement the required hooks to support recovery in the presence of failures.
    2. -
  2. It also does not utilize a transactional back end resource.
    3. -
  3. Only one Web service participates in the protocol. As WS-BA is a coordination protocol, it is best suited to multi-participant scenarios.
    4. -
-

For a more complete example, please see the XTS demonstrator application that ships with the JBossTS project: http://www.jboss.org/jbosstm.

-

It is also assumed tht you have an understanding of WS-BusinessActivity. For more details, read the XTS documentation -that ships with the JBossTS project, which can be downloaded here: http://www.jboss.org/jbosstm/downloads/JBOSSTS_4_16_0_Final

-

The application consists of a single JAX-WS web service that is deployed within a war archive. It is tested with a JBoss -Arquillian enabled JUnit test.

-

When running the org.jboss.as.quickstarts.wsba.participantcompletion.simple.ClientTest#testSuccess() method, the -following steps occur:

-
    -
  1. A new Business Activity is created by the client.
    2. -
  2. An operation on a WS-BA enabled Web service is invoked by the client.
    3. -
  3. The JaxWSHeaderContextProcessor in the WS Client handler chain inserts the BA context into the outgoing SOAP message
    4. -
  4. When the service receives the SOAP request, it's JaxWSHeaderContextProcessor in it's handler chain inspects the BA context and associates the request with this BA.
    5. -
  5. The Web service operation is invoked...
    6. -
  6. A participant is enlisted in this BA. This allows the Web Service logic to respond to protocol events, such as compensate and close.
    7. -
  7. The service invokes the business logic. In this case, a String value is added to the set.
    8. -
  8. The backend resource is prepared. This ensures that the Backend resource can undo or make permanent the change when told to do so by the coordinator.
    9. -
  9. Providing the above steps where successful, the service notifies the coordinator that it has completed. The service has now made it's changes visible and is not holding any locks. Allowing the service to notify completion is an optimisation that prevents the holding of locks, whilst waiting for other participants to complete. This notification is required as the Service participates in the ParticipantCompletion protocol.
    10. -
  10. The client can then decide to complete or cancel the BA. If the client decides to complete, all participants will be told to close. If the participant decides to cancel, all participants will be told to compensate.
    11. -
-

There are other tests that show:

-

What happens when an application exception is thrown by the service.

-

How the client can cancel a BA.

-

System requirements

-

All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven -3.0 or better.

-

The application this project produces is designed to be run on a JBoss AS 7 or EAP 6. -The following instructions target JBoss AS 7, but they also apply to JBoss EAP 6.

-

With the prerequisites out of the way, you're ready to build and deploy.

-

Deploying the application

-

First you need to start JBoss AS 7 (7.1.0.CR1 or above, or EAP 6), with the XTS sub system enabled, this is enabled through an optional server configuration (standalone-xts.xml). To do this, run the following commands, from within the top-level directory of JBossAS:

-
./bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml | egrep "started|stdout"
-
-

Note, the pipe to egrep (| egrep "started|stdout") is useful to just show when the server has started and the output from these tests. For normal operation, this pipe can be removed.

-

or if you are using windows

-
./bin/standalone.bat --server-config=../../docs/examples/configs/standalone-xts.xml
-
-

To test the application run:

-
mvn clean test -Parq-jbossas-remote
-
-

The following expected output should appear. The output explains what actually went on when these tests ran.

-

Test success:

-
11:41:02,386 INFO  [stdout] (management-handler-threads - 6) Starting 'testSuccess'. This test invokes a WS within a BA. The BA is later closed, which causes the WS call to complete successfully.
-11:41:02,386 INFO  [stdout] (management-handler-threads - 6) [CLIENT] Creating a new Business Activity
-11:41:02,386 INFO  [stdout] (management-handler-threads - 6) [CLIENT] Beginning Business Activity (All calls to Web services that support WS-BA wil be included in this activity)
-11:41:02,927 INFO  [stdout] (management-handler-threads - 6) [CLIENT] invoking addValueToSet(1) on WS
-11:41:03,233 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] invoked addValueToSet('1')
-11:41:03,233 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Enlisting a participant into the BA
-11:41:03,336 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Invoking the back-end business logic
-11:41:03,336 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Prepare the backend resource and if successful notify the coordinator that we have completed our work
-11:41:03,337 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Prepare successful, notifying coordinator of completion
-11:41:03,660 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) SetParticipantBA.confirmCompleted('true')
-11:41:03,660 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Participant.confirmCompleted('true') (This tells the participant that compensation information has been logged and that it is safe to commit any changes.)
-11:41:03,660 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Commit the backend resource (e.g. commit any changes to databases so that they are visible to others)
-11:41:03,779 INFO  [stdout] (management-handler-threads - 6) [CLIENT] Closing Business Activity (This will cause the BA to complete successfully)
-11:41:04,330 INFO  [stdout] (TaskWorker-2) [SERVICE] Participant.close (The participant knows that this BA is now finished and can throw away any temporary state)
-
-

Test cancel:

-
11:41:04,721 INFO  [stdout] (management-handler-threads - 5) Starting 'testCancel'. This test invokes a WS within a BA. The BA is later cancelled, which causes these WS call to be compensated.
-11:41:04,721 INFO  [stdout] (management-handler-threads - 5) [CLIENT] Creating a new Business Activity
-11:41:04,721 INFO  [stdout] (management-handler-threads - 5) [CLIENT] Beginning Business Activity (All calls to Web services that support WS-BA will be included in this activity)
-11:41:04,781 INFO  [stdout] (management-handler-threads - 5) [CLIENT] invoking addValueToSet(1) on WS
-11:41:05,133 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] invoked addValueToSet('1')
-11:41:05,134 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Enlisting a participant into the BA
-11:41:05,241 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Invoking the back-end business logic
-11:41:05,242 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Prepare the backend resource and if successful notify the coordinator that we have completed our work
-11:41:05,242 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Prepare successful, notifying coordinator of completion
-11:41:05,305 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) SetParticipantBA.confirmCompleted('true')
-11:41:05,305 INFO  [stdout] (http-localhost-127.0.0.1-8080-1) [SERVICE] Participant.confirmCompleted('true') (This tells the participant that compensation information has been logged and that it is safe to commit any changes.)
-
-

You can also start JBoss AS 7 and run the tests within Eclipse. See the JBoss AS 7 -Getting Started Guide for Developers for more information.

-

Importing the project into an IDE

-

If you created the project using the Maven archetype wizard in your IDE -(Eclipse, NetBeans or IntelliJ IDEA), then there is nothing to do. You should -already have an IDE project.

-

Detailed instructions for using Eclipse with JBoss AS 7 are provided in the -JBoss AS 7 Getting Started Guide for Developers.

-

If you created the project from the commandline using archetype:generate, then -you need to import the project into your IDE. If you are using NetBeans 6.8 or -IntelliJ IDEA 9, then all you have to do is open the project as an existing -project. Both of these IDEs recognize Maven projects natively.

-

Downloading the sources and Javadocs

-

If you want to be able to debug into the source code or look at the Javadocs -of any library in the project, you can run either of the following two -commands to pull them into your local repository. The IDE should then detect -them.

-
mvn dependency:sources
-mvn dependency:resolve -Dclassifier=javadoc
-
\ No newline at end of file