incubator-aries-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From z..@apache.org
Subject svn commit: r1040087 [1/5] - in /incubator/aries/branches/site: branches/ images/ resources/ trunk/ trunk/cgi-bin/ trunk/content/ trunk/content/images/ trunk/content/resources/ trunk/lib/ trunk/templates/
Date Mon, 29 Nov 2010 12:32:25 GMT
Author: zoe
Date: Mon Nov 29 12:32:22 2010
New Revision: 1040087

URL: http://svn.apache.org/viewvc?rev=1040087&view=rev
Log:
ARIES-502

Added:
    incubator/aries/branches/site/branches/
    incubator/aries/branches/site/trunk/
    incubator/aries/branches/site/trunk/cgi-bin/
    incubator/aries/branches/site/trunk/content/
    incubator/aries/branches/site/trunk/content/0.1-incubating.cwiki
    incubator/aries/branches/site/trunk/content/0.1-incubating.mdtext
    incubator/aries/branches/site/trunk/content/applications.cwiki
    incubator/aries/branches/site/trunk/content/applications.mdtext
    incubator/aries/branches/site/trunk/content/archived-releases.cwiki
    incubator/aries/branches/site/trunk/content/archived-releases.mdtext
    incubator/aries/branches/site/trunk/content/archiveinstructions.cwiki
    incubator/aries/branches/site/trunk/content/archiveinstructions.mdtext
    incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.cwiki
    incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.mdtext
    incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.cwiki
    incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.mdtext
    incubator/aries/branches/site/trunk/content/ariestrader.cwiki
    incubator/aries/branches/site/trunk/content/ariestrader.mdtext
    incubator/aries/branches/site/trunk/content/articles.cwiki
    incubator/aries/branches/site/trunk/content/articles.mdtext
    incubator/aries/branches/site/trunk/content/blog-sample.cwiki
    incubator/aries/branches/site/trunk/content/blog-sample.mdtext
    incubator/aries/branches/site/trunk/content/blogsample-0.1-incubating.cwiki
    incubator/aries/branches/site/trunk/content/blogsample-0.1-incubating.mdtext
    incubator/aries/branches/site/trunk/content/blueprint.cwiki
    incubator/aries/branches/site/trunk/content/blueprint.mdtext
    incubator/aries/branches/site/trunk/content/blueprintannotation.cwiki
    incubator/aries/branches/site/trunk/content/blueprintannotation.mdtext
    incubator/aries/branches/site/trunk/content/blueprinthelloworldtutorial.cwiki
    incubator/aries/branches/site/trunk/content/blueprinthelloworldtutorial.mdtext
    incubator/aries/branches/site/trunk/content/boardreports.cwiki
    incubator/aries/branches/site/trunk/content/boardreports.mdtext
    incubator/aries/branches/site/trunk/content/building-aries-in-eclipse.cwiki
    incubator/aries/branches/site/trunk/content/building-aries-in-eclipse.mdtext_bak
    incubator/aries/branches/site/trunk/content/buildingaries.cwiki
    incubator/aries/branches/site/trunk/content/buildingaries.mdtext
    incubator/aries/branches/site/trunk/content/community.cwiki
    incubator/aries/branches/site/trunk/content/community.mdtext
    incubator/aries/branches/site/trunk/content/compliancetesting.cwiki
    incubator/aries/branches/site/trunk/content/compliancetesting.mdtext
    incubator/aries/branches/site/trunk/content/december-2009.cwiki
    incubator/aries/branches/site/trunk/content/december-2009.mdtext
    incubator/aries/branches/site/trunk/content/development.cwiki
    incubator/aries/branches/site/trunk/content/development.mdtext
    incubator/aries/branches/site/trunk/content/documentation.cwiki
    incubator/aries/branches/site/trunk/content/documentation.mdtext
    incubator/aries/branches/site/trunk/content/downloads.cwiki
    incubator/aries/branches/site/trunk/content/downloads.mdtext
    incubator/aries/branches/site/trunk/content/ebamavenpluginproject.cwiki
    incubator/aries/branches/site/trunk/content/ebamavenpluginproject.mdtext
    incubator/aries/branches/site/trunk/content/gettinginvolved.cwiki
    incubator/aries/branches/site/trunk/content/gettinginvolved.mdtext
    incubator/aries/branches/site/trunk/content/goatsample.cwiki
    incubator/aries/branches/site/trunk/content/goatsample.mdtext
    incubator/aries/branches/site/trunk/content/greetertutorial.cwiki
    incubator/aries/branches/site/trunk/content/greetertutorial.mdtext
    incubator/aries/branches/site/trunk/content/how-to-run-the-osgi-enterprise-ct.cwiki
    incubator/aries/branches/site/trunk/content/how-to-run-the-osgi-enterprise-ct.mdtext
    incubator/aries/branches/site/trunk/content/images/
      - copied from r1039369, incubator/aries/branches/site/images/
    incubator/aries/branches/site/trunk/content/index.cwiki
    incubator/aries/branches/site/trunk/content/index.mdtext
    incubator/aries/branches/site/trunk/content/integrators-guide.cwiki
    incubator/aries/branches/site/trunk/content/integrators-guide.mdtext
    incubator/aries/branches/site/trunk/content/jndiproject.cwiki
    incubator/aries/branches/site/trunk/content/jndiproject.mdtext
    incubator/aries/branches/site/trunk/content/jpaproject.cwiki
    incubator/aries/branches/site/trunk/content/jpaproject.mdtext
    incubator/aries/branches/site/trunk/content/june-2010.cwiki
    incubator/aries/branches/site/trunk/content/june-2010.mdtext
    incubator/aries/branches/site/trunk/content/mailinglists.cwiki
    incubator/aries/branches/site/trunk/content/mailinglists.mdtext
    incubator/aries/branches/site/trunk/content/maintainingthewebpages.cwiki
    incubator/aries/branches/site/trunk/content/maintainingthewebpages.mdtext
    incubator/aries/branches/site/trunk/content/march-2010.cwiki
    incubator/aries/branches/site/trunk/content/march-2010.mdtext
    incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.cwiki
    incubator/aries/branches/site/trunk/content/maven-best-practice-in-aries.mdtext
    incubator/aries/branches/site/trunk/content/moduledependencies.cwiki
    incubator/aries/branches/site/trunk/content/moduledependencies.mdtext
    incubator/aries/branches/site/trunk/content/modules.cwiki
    incubator/aries/branches/site/trunk/content/modules.mdtext
    incubator/aries/branches/site/trunk/content/navigation.cwiki
    incubator/aries/branches/site/trunk/content/navigation.mdtext
    incubator/aries/branches/site/trunk/content/november-2009.cwiki
    incubator/aries/branches/site/trunk/content/november-2009.mdtext
    incubator/aries/branches/site/trunk/content/october-2009.cwiki
    incubator/aries/branches/site/trunk/content/october-2009.mdtext
    incubator/aries/branches/site/trunk/content/overview.cwiki
    incubator/aries/branches/site/trunk/content/overview.mdtext
    incubator/aries/branches/site/trunk/content/people.cwiki
    incubator/aries/branches/site/trunk/content/people.mdtext
    incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.cwiki
    incubator/aries/branches/site/trunk/content/pointerstoosgispecifications.mdtext
    incubator/aries/branches/site/trunk/content/releasenotes.cwiki
    incubator/aries/branches/site/trunk/content/releasenotes.mdtext
    incubator/aries/branches/site/trunk/content/releasingaries.cwiki
    incubator/aries/branches/site/trunk/content/releasingaries.mdtext
    incubator/aries/branches/site/trunk/content/resources/
      - copied from r1039369, incubator/aries/branches/site/resources/
    incubator/aries/branches/site/trunk/content/samples.cwiki
    incubator/aries/branches/site/trunk/content/samples.mdtext
    incubator/aries/branches/site/trunk/content/september-2010.cwiki
    incubator/aries/branches/site/trunk/content/september-2010.mdtext
    incubator/aries/branches/site/trunk/content/site.cwiki
    incubator/aries/branches/site/trunk/content/site.mdtext
    incubator/aries/branches/site/trunk/content/sitemap.cwiki
    incubator/aries/branches/site/trunk/content/sitemap.mdtext
    incubator/aries/branches/site/trunk/content/spi-fly.cwiki
    incubator/aries/branches/site/trunk/content/spi-fly.mdtext
    incubator/aries/branches/site/trunk/content/sponsorship.cwiki
    incubator/aries/branches/site/trunk/content/sponsorship.mdtext
    incubator/aries/branches/site/trunk/content/testresults.cwiki
    incubator/aries/branches/site/trunk/content/testresults.mdtext
    incubator/aries/branches/site/trunk/content/transactionsproject.cwiki
    incubator/aries/branches/site/trunk/content/transactionsproject.mdtext
    incubator/aries/branches/site/trunk/content/tutorials.cwiki
    incubator/aries/branches/site/trunk/content/tutorials.mdtext
    incubator/aries/branches/site/trunk/lib/
    incubator/aries/branches/site/trunk/lib/path.pm
    incubator/aries/branches/site/trunk/lib/view.pm
    incubator/aries/branches/site/trunk/templates/
    incubator/aries/branches/site/trunk/templates/navigation.mdtext
    incubator/aries/branches/site/trunk/templates/standard.html
    incubator/aries/branches/site/trunk/templates/standard.html_comdev
    incubator/aries/branches/site/trunk/templates/standard_markdown.html
Removed:
    incubator/aries/branches/site/images/
    incubator/aries/branches/site/resources/

Added: incubator/aries/branches/site/trunk/content/0.1-incubating.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/0.1-incubating.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/0.1-incubating.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/0.1-incubating.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,58 @@
+h1. Apache Aries 0.1-incubating release
+Apache Aries delivers a set of pluggable Java components enabling an enterprise OSGi application programming model.
+Apache Aries modules are distributed in source and binary form. Alternatively you may checkout the source from Subversion and build Aries yourself. Otherwise, the releases below are available for download. These [KEYS|http://www.apache.org/dist/incubator/aries/KEYS] can be used to verify the release archive.
+All Apache Aries products are distributed under the terms of The Apache Software License (version 2.0). See the LICENSE file included in each distribution for additional license information.
+h3. Samples
+The easiest way to use the samples is to download the source zip, navigate to the appropriate 'assembly' module and run mvn install to download all the released  binary artifacts. Alternatively you can build the entire source.
+|| Sub project || Module || Version || Download || Comments ||
+| Aries Samples | | 0.1 | {ariesarchive:zip}samples-0.1-incubating-source-release{ariesarchive} | Source, ready to build |
+| | AriesTrader | 0.1 | \- | [AriesTrader sample instructions|ARIES:AriesTrader]
+| | AriesTrader JDBC app | 0.1 | {ariesarchive:eba}org.apache.aries.samples.ariestrader.jdbc-0.1-incubating{ariesarchive} | AriesTrader app with JDBC persistence only |
+| | AriesTrader JPA & JDBC app | 0.1 | {ariesarchive:eba}org.apache.aries.samples.ariestrader.all-0.1-incubating{ariesarchive} | AriesTrader app with all available persistence methods |
+| | Blog | 0.1 | \- | [Blog Sample instructions|ARIES:Blog Sample] || 
+| | Blog JDBC app | 0.1 | {ariesarchive:eba}org.apache.aries.samples.blog.jdbc.eba-0.1-incubating{ariesarchive} | Blog app based on JDBC |
+| | Blog JPA app | 0.1 | {ariesarchive:eba}org.apache.aries.samples.blog.jpa.eba-0.1-incubating{ariesarchive} | Blog app based on JPA |
+| | Blueprint HelloWorld | 0.1 | \- | |
+| | Blueprint ID Verifier| 0.1 | \- | |
+h3. Project components
+|| Sub project || Module || Version || Binary || Source ||
+|Application | | 0.1 | \- | {ariesarchive:zip}application-0.1-incubating-source-release{ariesarchive} || 
+| |application-api | 0.1 | {ariesarchive:jar}org.apache.aries.application.api-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.ap
+i-0.1-incubating-sources{ariesarchive} |
+| | application-bundle | 0.1 | {ariesarchive:jar}org.apache.aries.application-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application-0.1-incubating-sources{ariesarchive} |
+| | application-converters | 0.1 | {ariesarchive:jar}org.apache.aries.application.converters-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.converters-0.1-incubating-sources{ariesarchive} |
+| | application-install | 0.1 | {ariesarchive:jar}org.apache.aries.application.install-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.install-0.1-incubating-sources{ariesarchive} |
+| | application-management | 0.1 | {ariesarchive:jar}org.apache.aries.application.management-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.
+application.management-0.1-incubating-sources{ariesarchive} || 
+| | application-obr-resolver | 0.1 | {ariesarchive:jar}org.apache.aries.application.resolver.obr-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.resolver.obr-0.1-incubating-sources{ariesarchive} |
+| | application-runtime | 0.1 | {ariesarchive:jar}org.apache.aries.application.runtime-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.runtime-0.1-incubating-sources{ariesarchive} |
+| | application-utils | 0.1 | {ariesarchive:jar}org.apache.aries.application.utils-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.application.utils-0.1-incubating-sources{ariesarchive} |
+| Blueprint | | 0.1 | \- | {ariesarchive:zip}blueprint-0.1-incubating-source-release{ariesarchive} |
+| | blueprint-api | 0.1 | {ariesarchive:jar}org.apache.aries.blueprint.api-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.blueprint.api-0.1-incubating-sources{ariesarchive} |
+| | blueprint-bundle | 0.1 | {ariesarchive:jar}org.apache.aries.blueprint-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.blueprint-0.1-incubating-sources{ariesarchive} |
+| | blueprint-cm | 0.1 | {ariesarchive:jar}org.apache.aries.blueprint.cm-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.blueprint.cm-0.1-incubating-sources{ariesarchive} |
+| | blueprint-core | 0.1 | {ariesarchive:jar}org.apache.aries.blueprint.core-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.blueprint.core-0.1-incubating-sources{ariesarchive} |
+| eba-maven-plugin | | 0.1 | \- | {ariesarchive:zip}eba-maven-plugin-0.1-incubating-source-release{ariesarchive} |
+| | \- | 0.1 | {ariesarchive:jar}eba-maven-plugin-0.1-incubating{ariesarchive} | {ariesarchive:jar}eba-maven-plugin-0.1-incubating-sources{ariesarchive} |
+| JMX | | 0.1 | \- | {ariesarchive:zip}jmx-0.1-incubating-source-release{ariesarchive} |
+| | jmx-api | 0.1 | {ariesarchive:jar}org.apache.aries.jmx.api-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx.api-0.1-incubating-sources{ariesarchive} |
+| | jmx-blueprint-api | 0.1 | {ariesarchive:jar}org.apache.aries.jmx.blueprint.api-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx.blueprint.api-0.1-incubating-sources{ariesarchive} |
+| | jmx-blueprint-bundle | 0.1 | {ariesarchive:jar}org.apache.aries.jmx.blueprint-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx.blueprint-0.1-incubating-sources{ariesarchive} |
+| | jmx-blueprint-core | 0.1 | {ariesarchive:jar}org.apache.aries.jmx.blueprint.core-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx.blueprint.core-0.1-incubating-sources{ariesarchive} |
+| | jmx-bundle | 0.1 | {ariesarchive:jar}org.apache.aries.jmx-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx-0.1-incubating-sources{ariesarchive} |
+| | jmx-core | 0.1 | {ariesarchive:jar}org.apache.aries.jmx.core-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jmx.core-0.1-incubating-sources{ariesarchive} |
+| JNDI | | 0.1 | \- | {ariesarchive:zip}jndi-0.1-incubating-source-release{ariesarchive} |
+| | jndi-bundle | 0.1 | {ariesarchive:jar}org.apache.aries.jndi-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jndi-0.1-incubating-sources{ariesarchive} |
+| | jndi-core | 0.1 | {ariesarchive:jar}org.apache.aries.jndi.core-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jndi.core-0.1-incubating-sources{ariesarchive} |
+| | jndi-url | 0.1 | {ariesarchive:jar}org.apache.aries.jndi.url-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jndi.url-0.1-incubating-sources{ariesarchive} |
+| JPA | | 0.1 | \- | {ariesarchive:zip}jpa-0.1-incubating-source-release{ariesarchive} |
+| | jpa-api | 0.1 | {ariesarchive:jar}org.apache.aries.jpa.api-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jpa.api-0.1-incubating-sources{ariesarchive} |
+| | jpa-blueprint-aries | 0.1 | {ariesarchive:jar}org.apache.aries.jpa.blueprint.aries-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jpa.blueprint.aries-0.1-incubating-sources{ariesarchive} |
+| | jpa-container | 0.1 | {ariesarchive:jar}org.apache.aries.jpa.container-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jpa.container-0.1-incubating-sources{ariesarchive} |
+| | jpa-container-context | 0.1 | {ariesarchive:jar}org.apache.aries.jpa.container.context-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.jpa.container.context-0.1-incubating-sources{ariesarchive} |
+| Transaction | | 0.1 | \- | {ariesarchive:zip}transaction-0.1-incubating-source-release{ariesarchive} |
+| | transaction-blueprint | 0.1 | {ariesarchive:jar}org.apache.aries.transaction.blueprint-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.transaction.blueprint-0.1-incubating-sources{ariesarchive} |
+| | transaction-manager | 0.1 | {ariesarchive:jar}org.apache.aries.transaction.manager-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.transaction.manager-0.1-incubating-sources{ariesarchive} |
+| | transaction-wrappers | 0.1 | {ariesarchive:jar}org.apache.aries.transaction.wrappers-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.transaction.wrappers-0.1-incubating-sources{ariesarchive} |
+| Util | | 0.1 | \- | {ariesarchive:zip}org.apache.aries.util-0.1-incubating-source-release{ariesarchive} |
+| | \- | 0.1 | {ariesarchive:jar}org.apache.aries.util-0.1-incubating{ariesarchive} | {ariesarchive:jar}org.apache.aries.util-0.1-incubating-sources{ariesarchive} |

Added: incubator/aries/branches/site/trunk/content/0.1-incubating.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/0.1-incubating.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/0.1-incubating.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/0.1-incubating.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,202 @@
+Title: 0.1-incubating
+<a name="0.1-incubating-ApacheAries0.1-incubatingrelease"></a>
+# Apache Aries 0.1-incubating release
+Apache Aries delivers a set of pluggable Java components enabling an
+enterprise OSGi application programming model.
+Apache Aries modules are distributed in source and binary form.
+Alternatively you may checkout the source from Subversion and build Aries
+yourself. Otherwise, the releases below are available for download. These [KEYS](http://www.apache.org/dist/incubator/aries/KEYS)
+ can be used to verify the release archive.
+All Apache Aries products are distributed under the terms of The Apache
+Software License (version 2.0). See the LICENSE file included in each
+distribution for additional license information.
+<a name="0.1-incubating-Samples"></a>
+### Samples
+The easiest way to use the samples is to download the source zip, navigate
+to the appropriate 'assembly' module and run mvn install to download all
+the released  binary artifacts. Alternatively you can build the entire
+source.
+<table>
+<tr><th> Sub project </th><th> Module </th><th> Version </th><th> Download </th><th> Comments </th></tr>
+<tr><td> Aries Samples </td><td> </td><td> 0.1 </td><td>
+{ariesarchive:zip}samples-0.1-incubating-source-release{ariesarchive} </td><td>
+Source, ready to build </td></tr>
+<tr><td> </td><td> AriesTrader </td><td> 0.1 </td><td> \- </td><td> [AriesTrader sample instructions](aries:ariestrader.html)
+</tr>
+<tr><td> </td><td> AriesTrader JDBC app </td><td> 0.1 </td><td>
+{ariesarchive:eba}org.apache.aries.samples.ariestrader.jdbc-0.1-incubating{ariesarchive}
+</td><td> AriesTrader app with JDBC persistence only </td></tr>
+<tr><td> </td><td> AriesTrader JPA & JDBC app </td><td> 0.1 </td><td>
+{ariesarchive:eba}org.apache.aries.samples.ariestrader.all-0.1-incubating{ariesarchive}
+</td><td> AriesTrader app with all available persistence methods </td></tr>
+<tr><td> </td><td> Blog </td><td> 0.1 </td><td> \- </td><td> [Blog Sample instructions](aries:blog-sample.html)
+ </th></tr>
+<tr><td> </td><td> Blog JDBC app </td><td> 0.1 </td><td>
+{ariesarchive:eba}org.apache.aries.samples.blog.jdbc.eba-0.1-incubating{ariesarchive}
+</td><td> Blog app based on JDBC </td></tr>
+<tr><td> </td><td> Blog JPA app </td><td> 0.1 </td><td>
+{ariesarchive:eba}org.apache.aries.samples.blog.jpa.eba-0.1-incubating{ariesarchive}
+</td><td> Blog app based on JPA </td></tr>
+<tr><td> </td><td> Blueprint HelloWorld </td><td> 0.1 </td><td> \- </td><td> </td></tr>
+<tr><td> </td><td> Blueprint ID Verifier</td><td> 0.1 </td><td> \- </td><td> </td></tr>
+<a name="0.1-incubating-Projectcomponents"></a>
+### Project components
+<tr><th> Sub project </th><th> Module </th><th> Version </th><th> Binary </th><th> Source </th></tr>
+<tr><td>Application </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}application-0.1-incubating-source-release{ariesarchive}
+</th></tr>
+<tr><td> </td><td>application-api </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.api-0.1-incubating{ariesarchive}
+</td><td> {ariesarchive:jar}org.apache.aries.application.ap
+</tr>
+i-0.1-incubating-sources{ariesarchive} |
+<tr><td> </td><td> application-bundle </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> application-converters </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.converters-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application.converters-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> application-install </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.install-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application.install-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> application-management </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.management-0.1-incubating{ariesarchive}
+</td><td> {ariesarchive:jar}org.apache.aries.
+</tr>
+application.management-0.1-incubating-sources{ariesarchive} || 
+<tr><td> </td><td> application-obr-resolver </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.resolver.obr-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application.resolver.obr-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> application-runtime </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.runtime-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application.runtime-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> application-utils </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.application.utils-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.application.utils-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> Blueprint </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}blueprint-0.1-incubating-source-release{ariesarchive} </td></tr>
+<tr><td> </td><td> blueprint-api </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.api-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.api-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> blueprint-bundle </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.blueprint-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.blueprint-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> blueprint-cm </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.cm-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.cm-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> blueprint-core </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.core-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.blueprint.core-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> eba-maven-plugin </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}eba-maven-plugin-0.1-incubating-source-release{ariesarchive}
+</td></tr>
+<tr><td> </td><td> \- </td><td> 0.1 </td><td>
+{ariesarchive:jar}eba-maven-plugin-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}eba-maven-plugin-0.1-incubating-sources{ariesarchive} </td></tr>
+<tr><td> JMX </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}jmx-0.1-incubating-source-release{ariesarchive} </td></tr>
+<tr><td> </td><td> jmx-api </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.api-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.api-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jmx-blueprint-api </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint.api-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint.api-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jmx-blueprint-bundle </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jmx-blueprint-core </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint.core-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jmx.blueprint.core-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jmx-bundle </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jmx-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jmx-core </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.core-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jmx.core-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> JNDI </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}jndi-0.1-incubating-source-release{ariesarchive} </td></tr>
+<tr><td> </td><td> jndi-bundle </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jndi-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jndi-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jndi-core </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jndi.core-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jndi.core-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jndi-url </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jndi.url-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jndi.url-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> JPA </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}jpa-0.1-incubating-source-release{ariesarchive} </td></tr>
+<tr><td> </td><td> jpa-api </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jpa.api-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.jpa.api-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jpa-blueprint-aries </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jpa.blueprint.aries-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jpa.blueprint.aries-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jpa-container </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jpa.container-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jpa.container-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> jpa-container-context </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.jpa.container.context-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.jpa.container.context-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> Transaction </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}transaction-0.1-incubating-source-release{ariesarchive} </td></tr>
+<tr><td> </td><td> transaction-blueprint </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.transaction.blueprint-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.transaction.blueprint-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> transaction-manager </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.transaction.manager-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.transaction.manager-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> </td><td> transaction-wrappers </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.transaction.wrappers-0.1-incubating{ariesarchive}
+</td><td>
+{ariesarchive:jar}org.apache.aries.transaction.wrappers-0.1-incubating-sources{ariesarchive}
+</td></tr>
+<tr><td> Util </td><td> </td><td> 0.1 </td><td> \- </td><td>
+{ariesarchive:zip}org.apache.aries.util-0.1-incubating-source-release{ariesarchive}
+</td></tr>
+<tr><td> </td><td> \- </td><td> 0.1 </td><td>
+{ariesarchive:jar}org.apache.aries.util-0.1-incubating{ariesarchive} </td><td>
+{ariesarchive:jar}org.apache.aries.util-0.1-incubating-sources{ariesarchive}
+</td></tr>

Added: incubator/aries/branches/site/trunk/content/applications.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/applications.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/applications.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/applications.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,87 @@
+h1. Aries Applications
+
+An Aries application is a collection of one or more OSGi modules that together provide a coherent business function. An Aries application can consist of modules of many different types.  For example, a Aries application providing Web banking might consist of bundles with Web content (Web Application Bundles), bundles with Blueprint contexts, and bundles with JPA entities and persistence configuration (Persistence Bundles).  
+
+An Aries application isolates the OSGi services offered by its contained modules so that they are not visible outside the application unless explicitly configured to be exported from the application. Aries applications have several ways of accepting workloads: an Aries applications may include Web bundles for processing HTTP workloads; it may export one or more of the services offered by its contained modules to other Aries applications or for distribution as a Web service.  
+
+With the isolation runtime, each Aries application runs in its own isolated OSGi framework instance with its own OSGi service registry. Bundles in one Aries application cannot see bundles, services, or packages that are defined in another OSGi application, unless the bundles, services, or packages are explicitly shared by both applications. An Aries application can also load packages and consume OSGi services from a shared bundle space, that is, the OSGi framework instance that is the parent of all the isolated framework instances of the OSGi applications.
+
+h2. Structure of an Aries application
+
+An Aries application is packaged as a zip file with a '.eba' suffix. Its structure is as follows:
+
+{code:title=Sample Aries application structure}
+META-INF/APPLICATION.MF
+bundle1.jar
+bundle2.jar
+bundle3.jar
+{code}
+
+The file must contain either an APPLICATION.MF with at least one bundle listed in its Application-Content header (see below), or at least one bundle 'by value' within the .eba. No 'by value' bundles are required if a valid APPLICATION.MF is present. 
+
+Application metadata, APPLICATION.MF,  stored in the .eba file defines the isolation scope of the bundles that the OSGi application uses. An Aries applicaiton can also use metadata to permit some of its constituent bundles to be shared. Sharing in this way can reduce the memory and resource requirements of a system. Shared bundles must be provided by reference rather than contained directly in an application.
+
+h2. Aries Application Manifest
+
+An Aries Application is defined using a Manifest. The Aries manifest is located at META-INF/APPLICATION.MF and describes modularity at the application level. The manifest enumerates the modules that comprise the Aries application along with any OSGi services exported from, or referenced by, those modules.  The following is an example of an Aries manifest:
+
+{code:title=APPLICATION.MF}
+Manifest-Version: 1.0
+Application-ManifestVersion: 1.0
+Application-Name: Bank Account
+Application-SymbolicName: com.mybank.account.app
+Application-Version: 1.0
+Application-Content: 
+	com.mybank.account.bankWeb; version=1.0.0,
+	com.mybank.account.bankAccount; version=1.0.0,
+	com.mybank.account.common; version=1.0.0,
+	com.mybank.account.utility; version=1.0.0
+Use-Bundle: com.mybank.account.admin;version="[1.0.0,2.0.0)"
+Application-ExportService: com.mybank.account.service.AccountService
+Application-ImportService: com.mybank.security.UserAuthService;filter="(security=strong)"
+{code}
+
+The manifest headers are as follows:
+
+* Manifest-Version - a version number for the manifest format.
+* Application-ManifestVersion - identifies the application manifest version to which this manifest conforms
+* Application-Name - a human readable name for the application
+* Application-SymbolicName - a name to uniquely identify the application. Follows the same scheme as Bundle-SymbolicName.
+* Application-Version - uniquely identify the version of the application. The combination of symbolic name and version must be unique within an Aries application runtime.
+* Application-Content - a list of 'root' bundles to provision for the application. 'Version' identifies a version range for the bundle to be provisioned thus allowing flexibility. The version format is identical to that used for OSGi import (e.g. Import-Package).
+* Use-Bundle - a list of bundles bundles to use to satisfy the package dependencies of bundles in the Application-Content list. Each bundle in the Use-Bundle list must provide at least one package to at least one bundle in the Application-Content list. These bundles will be provisioned into the shared bundle space at run time.
+* Application-ExportService - a list of service interface names and optional filters identifying services provided by the application which can be accessed outside the application.
+* Application-ImportService - a list of service interface names and optional filters identifying services which the application would like to consume from outside the application.
+
+Often, you do not require a Use-Bundle header, but there are some situations where it is useful. You can use it to restrict the level at which sharing is possible. For example, you can ensure that an application uses the same bundle for package imports that it was tested with. Alternatively, you can ensure that two applications use the same bundle for package imports. By setting the restriction at application level, the bundle can remain flexible.
+
+h2. Aries Deployment Manifest
+
+The Aries application model allows for the possibility that the bundles listed in APPLICATION.MF's Application-Content header, plus those optionally included within a .eba file, may have unsatisfied package or service dependencies. Such missing dependencies may be obtained ('provisioned') from one or more bundle repositories. Aries will provide a generic 'Resolver' API which may be backed by technology such as [Felix OBR|http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html] or [Equinox p2|http://wiki.eclipse.org/Equinox_p2_Getting_Started]. Although it is possible to re-resolve an application every time it is installed, or even started, this may result in inconsistent behaviour as the contents of an associated bundle repository changes. Aries uses a second file, META-INF/DEPLOYMENT.MF to record a single consistent set of bundles that fully satisfy an application's dependencies. The bundles recorded in DEPLOYMENT.MF will be loaded into the runtime each time t
 he application is installed. A DEPLOYMENT.MF file will be generated if one does not exist, or honoured if provided. Here's an example:
+
+{code:title=DEPLOYMENT.MF}
+Manifest-Version: 1.0
+Application-Version: 1.0
+Application-SymbolicName: com.mybank.account.app
+Deployed-Content: com.mybank.account.bankWeb; deployed-version=1.0.0,
+	com.mybank.account.bankAccount; deployed-version=1.0.0,
+	com.mybank.account.common; deployed-version=1.2.0,
+	com.mybank.account.utility; deployed-version=1.0.0, 
+        com.mybank.utils.logging; deployed-version=1.3.1
+Provision-Bundle: com.mybank.account.delivery;deployed-version=1.0.1
+Import-Package: com.mybank.account.admin.login;version="1.0.1";bundle-symbolic-name="com.mybank.account.admin";bundle-version="[1.0.1,1.0.1]",com.mybank.account.delivery.bycar;version="[1.0.0,2.0.0)",javax.servlet;version="2.5.0"
+Deployed-Use-Bundle: com.mybank.account.admin;deployed-version=1.0.1
+{code}
+The manifest headers are as follows:
+* Manifest-Version - a version number for the manifest format.
+* Application-Version - uniquely identify the version of the application. Must match that in the associated APPLICATION.MF. 
+* Application-SymbolicName - a name to uniquely identify the application. Follows the same scheme as Bundle-SymbolicName. Must match that in the associated APPLICATION.MF. 
+* Deployed-Content: the complete list of bundles, with exact version numbers, that comprise the application and its dependencies. 
+* Deployed-Use-Bundle - a list of bundles that satisfy the package dependencies of bundles in the Deployed-Content list. Each element in the Deployed-Use-Bundle list must provide at least one package to at least one bundle in the Deployed-Content list. The Deployed-Use-Bundle list is an exact subset of the Use-Bundle list in the APPLICATION.MF. These bundles will be loaded into the shared bundle space at run time. Each bundle in the Deployed-Use-Bundle list is guaranteed to be wired to its dependent bundles in the Deployed-Content list at run time. 
+* Provision-Bundle - a list of additional bundles that are required as a result of resolving the OSGi application. Each bundle is loaded into the shared bundle space at run time.
+* Import-Package - a list of the packages that the bundles in the Deployed-Content list consume from the bundles in the Deployed-Use-Bundle and Provision-Bundle lists. For packages that are consumed from the Deployed-Use-Bundle list, the package import has ;bundle-symbolic-name and ;bundle-version attributes. 
+
+Versions in APPLICATION.MF are ranges: in DEPLOYMENT.MF they are exact. Hence we see Application-Content: com.mybank.account.common; version=1.0.0 having been interpreted as '1.0.0 or higher' and so resolved to 1.2.0. Also a common logging bundle at version 1.3.1 will be deployed with the application. 
+  
+
+

Added: incubator/aries/branches/site/trunk/content/applications.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/applications.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/applications.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/applications.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,181 @@
+Title: Applications
+<a name="Applications-AriesApplications"></a>
+# Aries Applications
+
+An Aries application is a collection of one or more OSGi modules that
+together provide a coherent business function. An Aries application can
+consist of modules of many different types.  For example, a Aries
+application providing Web banking might consist of bundles with Web content
+(Web Application Bundles), bundles with Blueprint contexts, and bundles
+with JPA entities and persistence configuration (Persistence Bundles).	
+
+An Aries application isolates the OSGi services offered by its contained
+modules so that they are not visible outside the application unless
+explicitly configured to be exported from the application. Aries
+applications have several ways of accepting workloads: an Aries
+applications may include Web bundles for processing HTTP workloads; it may
+export one or more of the services offered by its contained modules to
+other Aries applications or for distribution as a Web service.	
+
+With the isolation runtime, each Aries application runs in its own isolated
+OSGi framework instance with its own OSGi service registry. Bundles in one
+Aries application cannot see bundles, services, or packages that are
+defined in another OSGi application, unless the bundles, services, or
+packages are explicitly shared by both applications. An Aries application
+can also load packages and consume OSGi services from a shared bundle
+space, that is, the OSGi framework instance that is the parent of all the
+isolated framework instances of the OSGi applications.
+
+<a name="Applications-StructureofanAriesapplication"></a>
+## Structure of an Aries application
+
+An Aries application is packaged as a zip file with a '.eba' suffix. Its
+structure is as follows:
+
+<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>Sample Aries application structure</B></DIV><DIV class="codeContent panelContent">
+    META-INF/APPLICATION.MF
+    bundle1.jar
+    bundle2.jar
+    bundle3.jar
+
+
+The file must contain either an APPLICATION.MF with at least one bundle
+listed in its Application-Content header (see below), or at least one
+bundle 'by value' within the .eba. No 'by value' bundles are required if a
+valid APPLICATION.MF is present. 
+
+Application metadata, APPLICATION.MF,  stored in the .eba file defines the
+isolation scope of the bundles that the OSGi application uses. An Aries
+applicaiton can also use metadata to permit some of its constituent bundles
+to be shared. Sharing in this way can reduce the memory and resource
+requirements of a system. Shared bundles must be provided by reference
+rather than contained directly in an application.
+
+<a name="Applications-AriesApplicationManifest"></a>
+## Aries Application Manifest
+
+An Aries Application is defined using a Manifest. The Aries manifest is
+located at META-INF/APPLICATION.MF and describes modularity at the
+application level. The manifest enumerates the modules that comprise the
+Aries application along with any OSGi services exported from, or referenced
+by, those modules.  The following is an example of an Aries manifest:
+
+<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>APPLICATION.MF</B></DIV><DIV class="codeContent panelContent">
+    Manifest-Version: 1.0
+    Application-ManifestVersion: 1.0
+    Application-Name: Bank Account
+    Application-SymbolicName: com.mybank.account.app
+    Application-Version: 1.0
+    Application-Content: 
+    	com.mybank.account.bankWeb; version=1.0.0,
+    	com.mybank.account.bankAccount; version=1.0.0,
+    	com.mybank.account.common; version=1.0.0,
+    	com.mybank.account.utility; version=1.0.0
+    Use-Bundle: com.mybank.account.admin;version="[1.0.0,2.0.0)"
+    Application-ExportService: com.mybank.account.service.AccountService
+    Application-ImportService:
+com.mybank.security.UserAuthService;filter="(security=strong)"
+
+
+The manifest headers are as follows:
+
+* Manifest-Version - a version number for the manifest format.
+* Application-ManifestVersion - identifies the application manifest version
+to which this manifest conforms
+* Application-Name - a human readable name for the application
+* Application-SymbolicName - a name to uniquely identify the application.
+Follows the same scheme as Bundle-SymbolicName.
+* Application-Version - uniquely identify the version of the application.
+The combination of symbolic name and version must be unique within an Aries
+application runtime.
+* Application-Content - a list of 'root' bundles to provision for the
+application. 'Version' identifies a version range for the bundle to be
+provisioned thus allowing flexibility. The version format is identical to
+that used for OSGi import (e.g. Import-Package).
+* Use-Bundle - a list of bundles bundles to use to satisfy the package
+dependencies of bundles in the Application-Content list. Each bundle in the
+Use-Bundle list must provide at least one package to at least one bundle in
+the Application-Content list. These bundles will be provisioned into the
+shared bundle space at run time.
+* Application-ExportService - a list of service interface names and
+optional filters identifying services provided by the application which can
+be accessed outside the application.
+* Application-ImportService - a list of service interface names and
+optional filters identifying services which the application would like to
+consume from outside the application.
+
+Often, you do not require a Use-Bundle header, but there are some
+situations where it is useful. You can use it to restrict the level at
+which sharing is possible. For example, you can ensure that an application
+uses the same bundle for package imports that it was tested with.
+Alternatively, you can ensure that two applications use the same bundle for
+package imports. By setting the restriction at application level, the
+bundle can remain flexible.
+
+<a name="Applications-AriesDeploymentManifest"></a>
+## Aries Deployment Manifest
+
+The Aries application model allows for the possibility that the bundles
+listed in APPLICATION.MF's Application-Content header, plus those
+optionally included within a .eba file, may have unsatisfied package or
+service dependencies. Such missing dependencies may be obtained
+('provisioned') from one or more bundle repositories. Aries will provide a
+generic 'Resolver' API which may be backed by technology such as [Felix OBR](http://felix.apache.org/site/apache-felix-osgi-bundle-repository.html)
+ or [Equinox p2|http://wiki.eclipse.org/Equinox_p2_Getting_Started]
+. Although it is possible to re-resolve an application every time it is
+installed, or even started, this may result in inconsistent behaviour as
+the contents of an associated bundle repository changes. Aries uses a
+second file, META-INF/DEPLOYMENT.MF to record a single consistent set of
+bundles that fully satisfy an application's dependencies. The bundles
+recorded in DEPLOYMENT.MF will be loaded into the runtime each time the
+application is installed. A DEPLOYMENT.MF file will be generated if one
+does not exist, or honoured if provided. Here's an example:
+
+<DIV class="code panel" style="border-style: solid;border-width: 1px;"><DIV class="codeHeader panelHeader" style="border-bottom-width: 1px;border-bottom-style: solid;"><B>DEPLOYMENT.MF</B></DIV><DIV class="codeContent panelContent">
+    Manifest-Version: 1.0
+    Application-Version: 1.0
+    Application-SymbolicName: com.mybank.account.app
+    Deployed-Content: com.mybank.account.bankWeb; deployed-version=1.0.0,
+    	com.mybank.account.bankAccount; deployed-version=1.0.0,
+    	com.mybank.account.common; deployed-version=1.2.0,
+    	com.mybank.account.utility; deployed-version=1.0.0, 
+    	com.mybank.utils.logging; deployed-version=1.3.1
+    Provision-Bundle: com.mybank.account.delivery;deployed-version=1.0.1
+    Import-Package: com.mybank.account.admin.login;version="1.0.1";bundle-symbolic-name="com.mybank.account.admin";bundle-version="[1.0.1,1.0.1]
+",com.mybank.account.delivery.bycar;version="[1.0.0,2.0.0)",javax.servlet;version="2.5.0"
+    Deployed-Use-Bundle: com.mybank.account.admin;deployed-version=1.0.1
+
+The manifest headers are as follows:
+* Manifest-Version - a version number for the manifest format.
+* Application-Version - uniquely identify the version of the application.
+Must match that in the associated APPLICATION.MF. 
+* Application-SymbolicName - a name to uniquely identify the application.
+Follows the same scheme as Bundle-SymbolicName. Must match that in the
+associated APPLICATION.MF. 
+* Deployed-Content: the complete list of bundles, with exact version
+numbers, that comprise the application and its dependencies. 
+* Deployed-Use-Bundle - a list of bundles that satisfy the package
+dependencies of bundles in the Deployed-Content list. Each element in the
+Deployed-Use-Bundle list must provide at least one package to at least one
+bundle in the Deployed-Content list. The Deployed-Use-Bundle list is an
+exact subset of the Use-Bundle list in the APPLICATION.MF. These bundles
+will be loaded into the shared bundle space at run time. Each bundle in the
+Deployed-Use-Bundle list is guaranteed to be wired to its dependent bundles
+in the Deployed-Content list at run time. 
+* Provision-Bundle - a list of additional bundles that are required as a
+result of resolving the OSGi application. Each bundle is loaded into the
+shared bundle space at run time.
+* Import-Package - a list of the packages that the bundles in the
+Deployed-Content list consume from the bundles in the Deployed-Use-Bundle
+and Provision-Bundle lists. For packages that are consumed from the
+Deployed-Use-Bundle list, the package import has ;bundle-symbolic-name and
+;bundle-version attributes. 
+
+Versions in APPLICATION.MF are ranges: in DEPLOYMENT.MF they are exact.
+Hence we see Application-Content: com.mybank.account.common; version=1.0.0
+having been interpreted as '1.0.0 or higher' and so resolved to 1.2.0. Also
+a common logging bundle at version 1.3.1 will be deployed with the
+application. 
+  
+
+

Added: incubator/aries/branches/site/trunk/content/archived-releases.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/archived-releases.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/archived-releases.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/archived-releases.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,3 @@
+h1. Archived releases
+
+[0.1-incubating]
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/archived-releases.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/archived-releases.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/archived-releases.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/archived-releases.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,5 @@
+Title: Archived Releases
+<a name="ArchivedReleases-Archivedreleases"></a>
+# Archived releases
+
+[0.1-incubating](0.1-incubating.html)

Added: incubator/aries/branches/site/trunk/content/archiveinstructions.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/archiveinstructions.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/archiveinstructions.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/archiveinstructions.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,5 @@
+h1. The Blog sample
+[BlogSample-0.1-incubating]
+
+h1. The AriesTrader sample
+[AriesTrader-0.1-incubating]
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/archiveinstructions.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/archiveinstructions.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/archiveinstructions.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/archiveinstructions.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,8 @@
+Title: ArchiveInstructions
+<a name="ArchiveInstructions-TheBlogsample"></a>
+# The Blog sample
+[BlogSample-0.1-incubating](blogsample-0.1-incubating.html)
+
+<a name="ArchiveInstructions-TheAriesTradersample"></a>
+# The AriesTrader sample
+[AriesTrader-0.1-incubating](ariestrader-0.1-incubating.html)

Added: incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,9 @@
+h1. Aries Programming Model
+
+The follow describes the programming model provided by the components of Apache Aries.
+
+[Applications]
+
+[Blueprint]
+
+[Transactions]

Added: incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/ariesprogrammingmodel.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,12 @@
+Title: AriesProgrammingModel
+<a name="AriesProgrammingModel-AriesProgrammingModel"></a>
+# Aries Programming Model
+
+The follow describes the programming model provided by the components of
+Apache Aries.
+
+[Applications](applications.html)
+
+[Blueprint](blueprint.html)
+
+[Transactions](transactions.html)

Added: incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,84 @@
+h1. The AriesTrader Sample
+
+
+h3. Prereqs 
+{note}
+The Derby installation prereq is only required when using the 0.1-incubating released version of the sample.  Subsequent releases will not require the installation of Derby.  
+
+Also note that the version of Derby used by the 0.1-incubating release and development versions of the AriesTrader Sample is 10.5.3.0. Since May 2010 the Derby tutorial points to the latest Derby release (10.6.x) - if this is installed the AriesTrader sample will not work. See [ARIES-317|https://issues.apache.org/jira/browse/ARIES-317]. For the present the best solution is to install Derby 10.5.3.
+{note}
+
+Follow the instructions [here|http://db.apache.org/derby/papers/DerbyTut/install_software.html#derby] to complete the following actions: Download Derby, Install Derby, Set DERBY_INSTALL, Configure Embedded Derby and then Verify Derby.
+
+
+h3. Creating the OSGi platform (equinox-test-harness) for AriesTrader 
+Download and unzip the source zip for the [latest release|ARIES:Downloads] of Aries Samples and build the equinox-test-harness module under ariestrader:
+{code}
+cd samples-0.1-incubating/ariestrader/assemblies/equinox-test-harness
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its dependencies.
+
+h3. Alternative build using Apache Aries trunk.
+As an alternative to using the released version you can also choose to work with the latest, unreleased code.  This will require the use of subversion to checkout the code followed by building the entire Apache Aries project.  Directions are provided here:  [Building Aries instructions|ARIES:BuildingAries].
+
+
+h3. Starting the Equinox Test Harness to run the AriesTrader sample
+AriesTrader needs a test harness to run in.  For this purpose we are using an Equinox assembly that pulls in all of the necessary dependencies.  
+
+The first task is to create the database necessary for AriesTrader:
+{noformat}
+cd [your_aries_installation]/ariestrader-sample/assemblies/equinox-test-harness/target
+export CLASSPATH=$DERBY_INSTALL/lib/derby.jar:$DERBY_INSTALL/lib/derbytools.jar:.
+java org.apache.derby.tools.ij tradeDB.sql
+{noformat}
+
+Next, start Aries in an OSGi framework using the Eclipse Equinox test harness
+{noformat}
+java -jar osgi-3.5.0.v20090520.jar -console
+{noformat}
+The OSGi console should start up, the 'ss' command should show the active bundles but the AriesTrader application is not yet installed (with the exception of the ariestrader derby datasource which is started with the test harness for convenience).  
+
+h3. Installing AriesTrader in the Equinox Test Harness
+To install the AriesTrader application simply copy the eba for AriesTrader into the target/load directory which was created when test harness containing Aries was started.  For convenience the AriesTraders EBAs are copied into the target directory as part of creating the OSGi Equinox test harness. 
+
+When using the "JDBC" only AriesTrader configuration which supports only jdbc persistence:
+{noformat}
+cp org.apache.aries.samples.ariestrader.jdbc-*.eba load/
+{noformat}
+
+When using the "All" AriesTrader configuration which supports all currently available persistence modes:
+{noformat}
+cp org.apache.aries.samples.ariestrader.all-*.eba load/
+{noformat}
+
+Now the 'ss' command should show all of the AriesTrader bundles in state 'ACTIVE'.
+
+If you subsequently delete org.apache.aries.samples.ariestrader.jdbc-*.eba or org.apache.aries.samples.ariestrader.all-*.eba from the target/load directory the application will be uninstalled.
+
+
+h3. Accessing and using the AriesTrader sample
+Point your browser at [http://localhost:8080/org.apache.aries.samples.ariestrader.web/]
+
+Select the "Configuration" tab and the "Configure AriesTrader run-time parameters" choice.  Then select from among the available runtime modes (defauls to JDBC).  Be sure to click "update config" to save your selection.
+
+At the moment the following persistence modes are available when using the "all" EBA:
+* JDBC persistence
+* JPA application managed entity manager persistence
+* JPA container managed entity managers using declarative transaction support  
+
+By default, the sample starts with JDBC persistence.  To select another persistence mechanism see the directions under "Accessing and using the AriesTrader sample. 
+ 
+After selecting the persistence mode you must create the AriesTrader Database tables and indexs.  Select the "Configuration" tab and the "(Re)-create AriesTrader Tables and Indexes". 
+
+Next, you must seed the database with test content.  Once again go to the "Configuration" tab but this time select "(Re)-populate AriesTrader Database" from the available choices to seed the database with a default set of users and stock quotes.  You will see a number of quotes (default is 400) and users (default is 200) created.
+
+Select the "Trading & Portfolios" tab to use the mock trade application or the "Primitives" tab to run some of the web primitive tests (PingJSPEL is not currently working).  You can also run the "Test AriesTrader Scenario" from the "Configuration" tab which will launch a new browser window and step through a trading scenario with each reload of the page.
+
+h3. About the AriesTrader Sample
+
+The AriesTrader sample is a modified version of the Apache Geronimo DayTrader sample.  It has been somewhat simplified and reorganized to support the Apache Aries programming model.  
+
+The AriesTrader sample bundles are organized like this:
+
+!ariesTraderOverview2.png!
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/ariestrader-0.1-incubating.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,143 @@
+Title: AriesTrader-0.1-incubating
+<a name="AriesTrader-0.1-incubating-TheAriesTraderSample"></a>
+# The AriesTrader Sample
+
+
+<a name="AriesTrader-0.1-incubating-Prereqs"></a>
+### Prereqs 
+{note}
+The Derby installation prereq is only required when using the
+0.1-incubating released version of the sample.	Subsequent releases will
+not require the installation of Derby.	
+
+Also note that the version of Derby used by the 0.1-incubating release and
+development versions of the AriesTrader Sample is 10.5.3.0. Since May 2010
+the Derby tutorial points to the latest Derby release (10.6.x) - if this is
+installed the AriesTrader sample will not work. See [ARIES-317](https://issues.apache.org/jira/browse/ARIES-317)
+. For the present the best solution is to install Derby 10.5.3.
+{note}
+
+Follow the instructions [here](http://db.apache.org/derby/papers/DerbyTut/install_software.html#derby)
+ to complete the following actions: Download Derby, Install Derby, Set
+DERBY_INSTALL, Configure Embedded Derby and then Verify Derby.
+
+
+<a name="AriesTrader-0.1-incubating-CreatingtheOSGiplatform(equinox-test-harness)forAriesTrader"></a>
+### Creating the OSGi platform (equinox-test-harness) for AriesTrader 
+Download and unzip the source zip for the [latest release](aries:downloads.html)
+ of Aries Samples and build the equinox-test-harness module under
+ariestrader:
+{code}
+cd samples-0.1-incubating/ariestrader/assemblies/equinox-test-harness
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its
+dependencies.
+
+<a name="AriesTrader-0.1-incubating-AlternativebuildusingApacheAriestrunk."></a>
+### Alternative build using Apache Aries trunk.
+As an alternative to using the released version you can also choose to work
+with the latest, unreleased code.  This will require the use of subversion
+to checkout the code followed by building the entire Apache Aries project. 
+Directions are provided here:  [Building Aries instructions](aries:buildingaries.html)
+.
+
+
+<a name="AriesTrader-0.1-incubating-StartingtheEquinoxTestHarnesstoruntheAriesTradersample"></a>
+### Starting the Equinox Test Harness to run the AriesTrader sample
+AriesTrader needs a test harness to run in.  For this purpose we are using
+an Equinox assembly that pulls in all of the necessary dependencies.  
+
+The first task is to create the database necessary for AriesTrader:
+
+    cd [your_aries_installation]
+/ariestrader-sample/assemblies/equinox-test-harness/target
+    export
+CLASSPATH=$DERBY_INSTALL/lib/derby.jar:$DERBY_INSTALL/lib/derbytools.jar:.
+    java org.apache.derby.tools.ij tradeDB.sql
+
+
+Next, start Aries in an OSGi framework using the Eclipse Equinox test
+harness
+
+    java -jar osgi-3.5.0.v20090520.jar -console
+
+The OSGi console should start up, the 'ss' command should show the active
+bundles but the AriesTrader application is not yet installed (with the
+exception of the ariestrader derby datasource which is started with the
+test harness for convenience).	
+
+<a name="AriesTrader-0.1-incubating-InstallingAriesTraderintheEquinoxTestHarness"></a>
+### Installing AriesTrader in the Equinox Test Harness
+To install the AriesTrader application simply copy the eba for AriesTrader
+into the target/load directory which was created when test harness
+containing Aries was started.  For convenience the AriesTraders EBAs are
+copied into the target directory as part of creating the OSGi Equinox test
+harness. 
+
+When using the "JDBC" only AriesTrader configuration which supports only
+jdbc persistence:
+
+    cp org.apache.aries.samples.ariestrader.jdbc-*.eba load/
+
+
+When using the "All" AriesTrader configuration which supports all currently
+available persistence modes:
+
+    cp org.apache.aries.samples.ariestrader.all-*.eba load/
+
+
+Now the 'ss' command should show all of the AriesTrader bundles in state
+'ACTIVE'.
+
+If you subsequently delete org.apache.aries.samples.ariestrader.jdbc-*.eba
+or org.apache.aries.samples.ariestrader.all-*.eba from the target/load
+directory the application will be uninstalled.
+
+
+<a name="AriesTrader-0.1-incubating-AccessingandusingtheAriesTradersample"></a>
+### Accessing and using the AriesTrader sample
+Point your browser at [http://localhost:8080/org.apache.aries.samples.ariestrader.web/](http://localhost:8080/org.apache.aries.samples.ariestrader.web/)
+
+Select the "Configuration" tab and the "Configure AriesTrader run-time
+parameters" choice.  Then select from among the available runtime modes
+(defauls to JDBC).  Be sure to click "update config" to save your
+selection.
+
+At the moment the following persistence modes are available when using the
+"all" EBA:
+* JDBC persistence
+* JPA application managed entity manager persistence
+* JPA container managed entity managers using declarative transaction
+support  
+
+By default, the sample starts with JDBC persistence.  To select another
+persistence mechanism see the directions under "Accessing and using the
+AriesTrader sample. 
+ 
+After selecting the persistence mode you must create the AriesTrader
+Database tables and indexs.  Select the "Configuration" tab and the
+"(Re)-create AriesTrader Tables and Indexes". 
+
+Next, you must seed the database with test content.  Once again go to the
+"Configuration" tab but this time select "(Re)-populate AriesTrader
+Database" from the available choices to seed the database with a default
+set of users and stock quotes.	You will see a number of quotes (default is
+400) and users (default is 200) created.
+
+Select the "Trading & Portfolios" tab to use the mock trade application or
+the "Primitives" tab to run some of the web primitive tests (PingJSPEL is
+not currently working).  You can also run the "Test AriesTrader Scenario"
+from the "Configuration" tab which will launch a new browser window and
+step through a trading scenario with each reload of the page.
+
+<a name="AriesTrader-0.1-incubating-AbouttheAriesTraderSample"></a>
+### About the AriesTrader Sample
+
+The AriesTrader sample is a modified version of the Apache Geronimo
+DayTrader sample.  It has been somewhat simplified and reorganized to
+support the Apache Aries programming model.  
+
+The AriesTrader sample bundles are organized like this:
+
+!ariesTraderOverview2.png!

Added: incubator/aries/branches/site/trunk/content/ariestrader.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariestrader.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariestrader.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/ariestrader.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,74 @@
+h1. The AriesTrader Sample
+
+
+h3. Prereqs 
+{note}
+These instructions are for the 0.2-incubating release of Aries. Instructions for older releases can be found [here|ArchiveInstructions]. In the 0.2-incubating release the AriesTrader sample was changed such that it is no longer required for you to install Derby independently.  The Derby version included in the sample is fully leveraged internally in the sample and therefore no additional Derby installation is required.  However, there are steps required to initialize the Database from within the sample itself (see instructions below).  
+{note}
+
+
+h3. Creating the OSGi platform (equinox-test-harness) for AriesTrader 
+Download and unzip the source zip for the [latest release|ARIES:Downloads] of Aries Samples and build the equinox-test-harness module under ariestrader:
+{code}
+cd samples-0.2-incubating/ariestrader/assemblies/equinox-test-harness
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its dependencies.
+
+h3. Alternative build using Apache Aries trunk.
+As an alternative to using the released version you can also choose to work with the latest, unreleased code.  This will require the use of subversion to checkout the code followed by building the entire Apache Aries project.  Directions are provided here:  [Building Aries instructions|ARIES:BuildingAries].
+
+
+h3. Starting the Equinox Test Harness to run the AriesTrader sample
+AriesTrader needs a test harness to run in.  For this purpose we are using an Equinox assembly that pulls in all of the necessary dependencies.  
+
+
+The first task is to start the Apache Aries modules in an OSGi framework using the Eclipse Equinox test harness
+{noformat}
+java -jar osgi-3.5.0.v20090520.jar -console
+{noformat}
+The OSGi console should start up, the 'ss' command should show the active bundles but the AriesTrader application is not yet installed (with the exception of the ariestrader derby datasource which is started with the test harness for convenience).  
+
+h3. Installing AriesTrader in the Equinox Test Harness
+To install the AriesTrader application simply copy the eba for AriesTrader into the target/load directory which was created when test harness containing Aries was started.  For convenience the AriesTraders EBAs are copied into the target directory as part of creating the OSGi Equinox test harness. 
+
+When using the "JDBC" only AriesTrader configuration which supports only jdbc persistence:
+{noformat}
+cp org.apache.aries.samples.ariestrader.jdbc-*.eba load/
+{noformat}
+
+When using the "All" AriesTrader configuration which supports all currently available persistence modes:
+{noformat}
+cp org.apache.aries.samples.ariestrader.all-*.eba load/
+{noformat}
+
+Now the 'ss' command should show all of the AriesTrader bundles in state 'ACTIVE'.
+
+If you subsequently delete org.apache.aries.samples.ariestrader.jdbc-*.eba or org.apache.aries.samples.ariestrader.all-*.eba from the target/load directory the application will be uninstalled.
+
+
+h3. Accessing and using the AriesTrader sample
+Point your browser at [http://localhost:8080/org.apache.aries.samples.ariestrader.web/]
+
+Select the "Configuration" tab and the "Configure AriesTrader run-time parameters" choice.  Then select from among the available runtime modes (defauls to JDBC).  Be sure to click "update config" to save your selection.
+
+At the moment the following persistence modes are available when using the "all" EBA:
+* JDBC persistence
+* JPA application managed entity manager persistence
+* JPA container managed entity managers using declarative transaction support  
+
+By default, the sample starts with JDBC persistence.  To select another persistence mechanism see the directions under "Accessing and using the AriesTrader sample. 
+ 
+After selecting the persistence mode you must create the AriesTrader Database tables and indexs.  Select the "Configuration" tab and the "(Re)-create AriesTrader Tables and Indexes". 
+
+Next, you must seed the database with test content.  Once again go to the "Configuration" tab but this time select "(Re)-populate AriesTrader Database" from the available choices to seed the database with a default set of users and stock quotes.  You will see a number of quotes (default is 400) and users (default is 200) created.
+
+Select the "Trading & Portfolios" tab to use the mock trade application or the "Primitives" tab to run some of the web primitive tests (PingJSPEL is not currently working).  You can also run the "Test AriesTrader Scenario" from the "Configuration" tab which will launch a new browser window and step through a trading scenario with each reload of the page.
+
+h3. About the AriesTrader Sample
+
+The AriesTrader sample is a modified version of the Apache Geronimo DayTrader sample.  It has been somewhat simplified and reorganized to support the Apache Aries programming model.  
+
+The AriesTrader sample bundles are organized like this:
+
+!ariesTraderOverview2.png!
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/ariestrader.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/ariestrader.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/ariestrader.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/ariestrader.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,130 @@
+Title: AriesTrader
+<a name="AriesTrader-TheAriesTraderSample"></a>
+# The AriesTrader Sample
+
+
+<a name="AriesTrader-Prereqs"></a>
+### Prereqs 
+{note}
+These instructions are for the 0.2-incubating release of Aries.
+Instructions for older releases can be found [here](archiveinstructions.html)
+. In the 0.2-incubating release the AriesTrader sample was changed such
+that it is no longer required for you to install Derby independently.  The
+Derby version included in the sample is fully leveraged internally in the
+sample and therefore no additional Derby installation is required. 
+However, there are steps required to initialize the Database from within
+the sample itself (see instructions below).  
+{note}
+
+
+<a name="AriesTrader-CreatingtheOSGiplatform(equinox-test-harness)forAriesTrader"></a>
+### Creating the OSGi platform (equinox-test-harness) for AriesTrader 
+Download and unzip the source zip for the [latest release](aries:downloads.html)
+ of Aries Samples and build the equinox-test-harness module under
+ariestrader:
+{code}
+cd samples-0.2-incubating/ariestrader/assemblies/equinox-test-harness
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its
+dependencies.
+
+<a name="AriesTrader-AlternativebuildusingApacheAriestrunk."></a>
+### Alternative build using Apache Aries trunk.
+As an alternative to using the released version you can also choose to work
+with the latest, unreleased code.  This will require the use of subversion
+to checkout the code followed by building the entire Apache Aries project. 
+Directions are provided here:  [Building Aries instructions](aries:buildingaries.html)
+.
+
+
+<a name="AriesTrader-StartingtheEquinoxTestHarnesstoruntheAriesTradersample"></a>
+### Starting the Equinox Test Harness to run the AriesTrader sample
+AriesTrader needs a test harness to run in.  For this purpose we are using
+an Equinox assembly that pulls in all of the necessary dependencies.  
+
+
+The first task is to start the Apache Aries modules in an OSGi framework
+using the Eclipse Equinox test harness
+
+    java -jar osgi-3.5.0.v20090520.jar -console
+
+The OSGi console should start up, the 'ss' command should show the active
+bundles but the AriesTrader application is not yet installed (with the
+exception of the ariestrader derby datasource which is started with the
+test harness for convenience).	
+
+<a name="AriesTrader-InstallingAriesTraderintheEquinoxTestHarness"></a>
+### Installing AriesTrader in the Equinox Test Harness
+To install the AriesTrader application simply copy the eba for AriesTrader
+into the target/load directory which was created when test harness
+containing Aries was started.  For convenience the AriesTraders EBAs are
+copied into the target directory as part of creating the OSGi Equinox test
+harness. 
+
+When using the "JDBC" only AriesTrader configuration which supports only
+jdbc persistence:
+
+    cp org.apache.aries.samples.ariestrader.jdbc-*.eba load/
+
+
+When using the "All" AriesTrader configuration which supports all currently
+available persistence modes:
+
+    cp org.apache.aries.samples.ariestrader.all-*.eba load/
+
+
+Now the 'ss' command should show all of the AriesTrader bundles in state
+'ACTIVE'.
+
+If you subsequently delete org.apache.aries.samples.ariestrader.jdbc-*.eba
+or org.apache.aries.samples.ariestrader.all-*.eba from the target/load
+directory the application will be uninstalled.
+
+
+<a name="AriesTrader-AccessingandusingtheAriesTradersample"></a>
+### Accessing and using the AriesTrader sample
+Point your browser at [http://localhost:8080/org.apache.aries.samples.ariestrader.web/](http://localhost:8080/org.apache.aries.samples.ariestrader.web/)
+
+Select the "Configuration" tab and the "Configure AriesTrader run-time
+parameters" choice.  Then select from among the available runtime modes
+(defauls to JDBC).  Be sure to click "update config" to save your
+selection.
+
+At the moment the following persistence modes are available when using the
+"all" EBA:
+* JDBC persistence
+* JPA application managed entity manager persistence
+* JPA container managed entity managers using declarative transaction
+support  
+
+By default, the sample starts with JDBC persistence.  To select another
+persistence mechanism see the directions under "Accessing and using the
+AriesTrader sample. 
+ 
+After selecting the persistence mode you must create the AriesTrader
+Database tables and indexs.  Select the "Configuration" tab and the
+"(Re)-create AriesTrader Tables and Indexes". 
+
+Next, you must seed the database with test content.  Once again go to the
+"Configuration" tab but this time select "(Re)-populate AriesTrader
+Database" from the available choices to seed the database with a default
+set of users and stock quotes.	You will see a number of quotes (default is
+400) and users (default is 200) created.
+
+Select the "Trading & Portfolios" tab to use the mock trade application or
+the "Primitives" tab to run some of the web primitive tests (PingJSPEL is
+not currently working).  You can also run the "Test AriesTrader Scenario"
+from the "Configuration" tab which will launch a new browser window and
+step through a trading scenario with each reload of the page.
+
+<a name="AriesTrader-AbouttheAriesTraderSample"></a>
+### About the AriesTrader Sample
+
+The AriesTrader sample is a modified version of the Apache Geronimo
+DayTrader sample.  It has been somewhat simplified and reorganized to
+support the Apache Aries programming model.  
+
+The AriesTrader sample bundles are organized like this:
+
+!ariesTraderOverview2.png!

Added: incubator/aries/branches/site/trunk/content/articles.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/articles.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/articles.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/articles.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,3 @@
+h1. Articles
+
+h3. [Jarek Gawor's article on Blueprint|http://www.ibm.com/developerworks/opensource/library/os-osgiblueprint/index.html]
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/articles.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/articles.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/articles.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/articles.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,6 @@
+Title: Articles
+<a name="Articles-Articles"></a>
+# Articles
+
+<a name="Articles-[JarekGawor'sarticleonBlueprint](http://www.ibm.com/developerworks/opensource/library/os-osgiblueprint/index.html)"></a>
+### [Jarek Gawor's article on Blueprint|http://www.ibm.com/developerworks/opensource/library/os-osgiblueprint/index.html]

Added: incubator/aries/branches/site/trunk/content/blog-sample.cwiki
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/blog-sample.cwiki?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/blog-sample.cwiki (added)
+++ incubator/aries/branches/site/trunk/content/blog-sample.cwiki Mon Nov 29 12:32:22 2010
@@ -0,0 +1,57 @@
+h1. The Blog Sample
+
+
+h2. Running the Blog Sample
+
+
+{note}
+These instructions are for the 0.2-incubating release of Aries. Instructions for older releases can be found [here|ArchiveInstructions]. In the 0.2-incubating release the sample was changed to use an in-memory database to avoid dependency on an explicit version of Derby. If you would prefer to use a database on disk check the instructions for the 0.1-incubating release. You will also need to modify datasource.xml (under blog-datasource) as indicated in the comments and then rebuild the sample.
+{note}
+
+h3. Create the OSGi platform for the Blog sample
+
+Download and unzip the source zip for the [latest release|ARIES:Downloads] of Aries Samples and build the blog-assembly module:
+{code}
+cd samples-0.2-incubating/blog/blog-assembly
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its dependencies.
+
+h3. Running the Blog sample
+
+Download the JDBC based Blog sample application (.eba file) from the [latest release|ARIES:Downloads]. Change directory to the blog-assembly target directory:
+
+{code}
+cd samples-0.2-incubating/blog-sample/blog-assembly/target
+{code}
+
+now start Aries in an OSGi framework (we're using Eclipse Equinox in this case)
+{code}
+java -jar osgi-3.5.0.v20090520.jar -console
+{code}
+
+The OSGi console should start up, the 'ss' command should show all of the Blog bundles in state 'ACTIVE'.
+
+Now start the blog application (.eba file) you downloaded earlier, by copying it into the load directory which was created when Aries started.
+
+Point your browser to [http://localhost:8080/org.apache.aries.samples.blog.web/]
+
+If you subsequently delete the .eba from the load directory the application will be uninstalled.
+
+h3. Running the sample using a JPA persistence layer
+
+The first blog sample application was written to use a JDBC persistence layer. There is a second application implemented to demonstrate the JPA capability
+
+To run the blog sample which uses the JPA persistence layer, start the OSGi framework, remove any previous copies of the blog sample from the target/load directory, then copy the Blog sample JPA .eba file into the load directory.
+
+Finally, after typing 'refresh' at the OSGi console, point your browser at [http://localhost:8080/org.apache.aries.samples.blog.web/]. You should see something that looks precisely the same as the blog sample running with the JDBC persistence layer, but this time running using the JPA persistence layer.
+
+h2. Using the latest, unreleased code
+
+If you prefer to use the very latest code from subversion, checkout and build the Aries trunk by following the [Building Aries instructions|ARIES:BuildingAries].
+
+h2. About the Blog sample
+
+The blog sample components can be visualised like this:
+
+!BlogSample.png!
\ No newline at end of file

Added: incubator/aries/branches/site/trunk/content/blog-sample.mdtext
URL: http://svn.apache.org/viewvc/incubator/aries/branches/site/trunk/content/blog-sample.mdtext?rev=1040087&view=auto
==============================================================================
--- incubator/aries/branches/site/trunk/content/blog-sample.mdtext (added)
+++ incubator/aries/branches/site/trunk/content/blog-sample.mdtext Mon Nov 29 12:32:22 2010
@@ -0,0 +1,88 @@
+Title: Blog Sample
+<a name="BlogSample-TheBlogSample"></a>
+# The Blog Sample
+
+
+<a name="BlogSample-RunningtheBlogSample"></a>
+## Running the Blog Sample
+
+
+{note}
+These instructions are for the 0.2-incubating release of Aries.
+Instructions for older releases can be found [here](archiveinstructions.html)
+. In the 0.2-incubating release the sample was changed to use an in-memory
+database to avoid dependency on an explicit version of Derby. If you would
+prefer to use a database on disk check the instructions for the
+0.1-incubating release. You will also need to modify datasource.xml (under
+blog-datasource) as indicated in the comments and then rebuild the sample.
+{note}
+
+<a name="BlogSample-CreatetheOSGiplatformfortheBlogsample"></a>
+### Create the OSGi platform for the Blog sample
+
+Download and unzip the source zip for the [latest release](aries:downloads.html)
+ of Aries Samples and build the blog-assembly module:
+{code}
+cd samples-0.2-incubating/blog/blog-assembly
+mvn install
+{code}
+This procedure will pull in the binaries from the latest release and its
+dependencies.
+
+<a name="BlogSample-RunningtheBlogsample"></a>
+### Running the Blog sample
+
+Download the JDBC based Blog sample application (.eba file) from the [latest release](aries:downloads.html)
+. Change directory to the blog-assembly target directory:
+
+{code}
+cd samples-0.2-incubating/blog-sample/blog-assembly/target
+{code}
+
+now start Aries in an OSGi framework (we're using Eclipse Equinox in this
+case)
+{code}
+java -jar osgi-3.5.0.v20090520.jar -console
+{code}
+
+The OSGi console should start up, the 'ss' command should show all of the
+Blog bundles in state 'ACTIVE'.
+
+Now start the blog application (.eba file) you downloaded earlier, by
+copying it into the load directory which was created when Aries started.
+
+Point your browser to [http://localhost:8080/org.apache.aries.samples.blog.web/](http://localhost:8080/org.apache.aries.samples.blog.web/)
+
+If you subsequently delete the .eba from the load directory the application
+will be uninstalled.
+
+<a name="BlogSample-RunningthesampleusingaJPApersistencelayer"></a>
+### Running the sample using a JPA persistence layer
+
+The first blog sample application was written to use a JDBC persistence
+layer. There is a second application implemented to demonstrate the JPA
+capability
+
+To run the blog sample which uses the JPA persistence layer, start the OSGi
+framework, remove any previous copies of the blog sample from the
+target/load directory, then copy the Blog sample JPA .eba file into the
+load directory.
+
+Finally, after typing 'refresh' at the OSGi console, point your browser at [http://localhost:8080/org.apache.aries.samples.blog.web/](http://localhost:8080/org.apache.aries.samples.blog.web/)
+. You should see something that looks precisely the same as the blog sample
+running with the JDBC persistence layer, but this time running using the
+JPA persistence layer.
+
+<a name="BlogSample-Usingthelatest,unreleasedcode"></a>
+## Using the latest, unreleased code
+
+If you prefer to use the very latest code from subversion, checkout and
+build the Aries trunk by following the [Building Aries instructions](aries:buildingaries.html)
+.
+
+<a name="BlogSample-AbouttheBlogsample"></a>
+## About the Blog sample
+
+The blog sample components can be visualised like this:
+
+!BlogSample.png!



Mime
View raw message