svn commit: r1708513 - in /servicemix/documentation/trunk/src/main/webapp: camel/troubleshooting.conf quickstart/activemq.conf quickstart/camel.conf quickstart/console.conf

[ks...@apache.org]

Author: ksobkowiak
Date: Tue Oct 13 21:15:01 2015
New Revision: 1708513

URL: http://svn.apache.org/viewvc?rev=1708513&view=rev
Log:
Replace osgi: commands with bundle: commands (closes #4)

Modified:
    servicemix/documentation/trunk/src/main/webapp/camel/troubleshooting.conf
    servicemix/documentation/trunk/src/main/webapp/quickstart/activemq.conf
    servicemix/documentation/trunk/src/main/webapp/quickstart/camel.conf
    servicemix/documentation/trunk/src/main/webapp/quickstart/console.conf

Modified: servicemix/documentation/trunk/src/main/webapp/camel/troubleshooting.conf
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/src/main/webapp/camel/troubleshooting.conf?rev=1708513&r1=1708512&r2=1708513&view=diff
==============================================================================
--- servicemix/documentation/trunk/src/main/webapp/camel/troubleshooting.conf (original)
+++ servicemix/documentation/trunk/src/main/webapp/camel/troubleshooting.conf Tue Oct 13 21:15:01 2015
@@ -5,6 +5,6 @@ This usually means that your route is tr
 
 Solution:
 # install the additional component
-# restart the bundle using the {{osg:restart <bundle id>}} command - you can find the bundle id for your route in the output of the {{osgi:list}} command
+# restart the bundle using the {{bundle:restart <bundle id>}} command - you can find the bundle id for your route in the output of the {{bundle:list}} command
 
 Refer to [Installing additional components|/users-guide/camel/installing-components] for more information about installing additional components.

Modified: servicemix/documentation/trunk/src/main/webapp/quickstart/activemq.conf
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/src/main/webapp/quickstart/activemq.conf?rev=1708513&r1=1708512&r2=1708513&view=diff
==============================================================================
--- servicemix/documentation/trunk/src/main/webapp/quickstart/activemq.conf (original)
+++ servicemix/documentation/trunk/src/main/webapp/quickstart/activemq.conf Tue Oct 13 21:15:01 2015
@@ -34,7 +34,7 @@ The first Blueprint XML file we'll creat
 </blueprint>
 {pygmentize}
 
-Save this file in ServiceMix' {{deploy}} folder and use {{osgi:list}} to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the {{activemq/input}} directory and see them being moved to {{activemq/output}}.
+Save this file in ServiceMix' {{deploy}} folder and use {{bundle:list}} to check on the bundle status as you did with the simple Camel example.  You should now be able to put files in the {{activemq/input}} directory and see them being moved to {{activemq/output}}.
 
 h2. Receiving the event messages
 After deploying the first XML file, you're obviously not seeing any events being logged yet.  The event messages are sent to an ActiveMQ queue, but there's nobody to receive the events yet.  Let's change that now by creating a second Blueprint XML file.

Modified: servicemix/documentation/trunk/src/main/webapp/quickstart/camel.conf
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/src/main/webapp/quickstart/camel.conf?rev=1708513&r1=1708512&r2=1708513&view=diff
==============================================================================
--- servicemix/documentation/trunk/src/main/webapp/quickstart/camel.conf (original)
+++ servicemix/documentation/trunk/src/main/webapp/quickstart/camel.conf Tue Oct 13 21:15:01 2015
@@ -37,7 +37,7 @@ If you do a {{log:display}} in the shell
 
 h2. Using the shell to manage the route
 
-Using {{osgi:list}}, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.
+Using {{bundle:list}}, you'll notice that your XML file has been transformed into a bundle and that the Blueprint container has been created to start your Camel route.
 
 !/quickstart/images/camel-sample-deploy.png!
 
@@ -45,12 +45,12 @@ From this output, you also learn that th
 
 First, stop the route with
 {pygmentize:lang=text}
-karaf@root> osgi:stop 200
+karaf@root> bundle:stop 200
 {pygmentize}
 
 The route is no longer active, so any files you copy into the {{orders/input}} folder will remain there for now.  As soon as you restart the route, the pending files will get moving again.
 
 {pygmentize:lang=text}
-karaf@root> osgi:start 200
+karaf@root> bundle:start 200
 {pygmentize}
 

Modified: servicemix/documentation/trunk/src/main/webapp/quickstart/console.conf
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/src/main/webapp/quickstart/console.conf?rev=1708513&r1=1708512&r2=1708513&view=diff
==============================================================================
--- servicemix/documentation/trunk/src/main/webapp/quickstart/console.conf (original)
+++ servicemix/documentation/trunk/src/main/webapp/quickstart/console.conf Tue Oct 13 21:15:01 2015
@@ -6,10 +6,10 @@ h2. Working with bundles
 
 When ServiceMix is first started, a whole set of bundles providing the core features for the product are being installed.  Let's use the command console to find out more about them...
 
-The {{osgi:list}} command can be used to get a list of all bundles currently installed.  Enter this
+The {{bundle:list}} command can be used to get a list of all bundles currently installed.  Enter this
 
 {pygmentize:lang=text}
-karaf@root> osgi:list
+karaf@root> bundle:list
 {pygmentize}
 
 This is what the output looks like if you run this on your ServiceMix instance.
@@ -26,7 +26,7 @@ For every bundle, you see:
 If you're looking for something specific in the list, you can use unix-like pipes and utilities to help you.  An example: to look for all Camel related bundles...
 
 {pygmentize:lang=text}
-karaf@root> osgi:list | grep camel
+karaf@root> bundle:list | grep camel
 {pygmentize}
 
 !/quickstart/images/osgi-list-pipegrep.png|title=osgi:list!
@@ -66,4 +66,4 @@ karaf@root> log:set INFO
 
 h2. ...and there's a lot more
 
-These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.
\ No newline at end of file
+These are obviously just a few examples of what the command shell is all about.  There are a lot more commands in the shell to help you deploy, monitor, manage and troubleshoot the applications you're building with ServiceMix.