ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1487787 - /ace/site/trunk/content/user-doc/getting-started.mdtext
Date Thu, 30 May 2013 08:51:34 GMT
Author: bramk
Date: Thu May 30 08:51:34 2013
New Revision: 1487787

URL: http://svn.apache.org/r1487787
Log:
ACE-139 Added some debug guidance

Modified:
    ace/site/trunk/content/user-doc/getting-started.mdtext

Modified: ace/site/trunk/content/user-doc/getting-started.mdtext
URL: http://svn.apache.org/viewvc/ace/site/trunk/content/user-doc/getting-started.mdtext?rev=1487787&r1=1487786&r2=1487787&view=diff
==============================================================================
--- ace/site/trunk/content/user-doc/getting-started.mdtext (original)
+++ ace/site/trunk/content/user-doc/getting-started.mdtext Thu May 30 08:51:34 2013
@@ -43,7 +43,7 @@ To start using ACE, you must first launc
 1. Navigate to the sub directory `target`.
 1. Start the target using `java -jar target.jar`
 
-## Working with ACE
+## Provisioning some bundles
 
 Apache ACE has both a Web UI and a [REST API](restapi.html) to interact with it. Both use
a similar workflow. You start by checking out a copy of the workspace, then you work on that
copy, and finally you commit your changes back to the server.
 
@@ -58,3 +58,12 @@ The following steps can be followed to g
 1. Drag a feature onto a distribution and again repeat this process until you've associated
all your features with their relevant distributions.
 1. Drag the distribution onto the target to associate it.
 1. Click on 'Store' to actually store changes on the server, which should trigger the actual
deployment of the artifacts to the target.
+
+## Validating that it worked
+
+After following the steps listed above the bundles should have been provisioned onto the
target. But did it work? There are a lot of things that can go wrong the first time. For exmaple,
remember you are provisioning into an empty OSGi framework so the deployment should be able
to resolve. Two ways to debug problems are;
+
+1. Inspect state and log of the target by double-clicking it in the webui.
+1. Start of by provisioning a shell to allow inspection of the target itself.
+
+Note: In version 1.0 the default binary target comes with a [Gogo shell](http://felix.apache.org/site/apache-felix-gogo.html)
pre-installed. It can be used right away.



Mime
View raw message