Page History

...

You should now be able to point your browser at: http://localhost:8080/^{Image Removed}

Build and Run the Console

...

Then point your web browse at http://localhost:8080/^{Image Removed}

You should be able to do things like

...

Then point your web browse at http://localhost:8080/^{Image Removed}

Embedding web console in your own web application.

See these relevant discussions for more information (more information to come soon):

http://camel.465427.n5.nabble.com/Embedded-web-console-td478885.html^{Image Removed}

http://camel.465427.n5.nabble.com/example-app-to-embed-camel-web-console-td4512075.html^{Image Removed}

REST API

Camel comes with a full RESTful API for interacting with the Camel context, the available endpoints and routes. You can browse details of the running API via http://localhost:8080/api^{Image Removed}

The web application uses mostly the same URIs for the HTML representation of a resource (e.g. /endpoints) as the JSON and XML representations. To help rendering the different representations in your browser you can append .xml, .html, .json or even .dot to URLs.

For example viewing these URLs are equivalent

URL	Same as
http://localhost:8080/endpoints.xmlImage Removed	http://localhost:8080/endpointsImage Removed with Accept header of text/xml or application/xml
http://localhost:8080/endpoints.jsonImage Removed	http://localhost:8080/endpointsImage Removed with Accept header of application/json
http://localhost:8080/routes.dotImage Removed	http://localhost:8080/routesImage Removed with Accept header of text/vnd.graphviz

...

Web Console provide route viewing and editing functionality. You can view your route via http://localhost:8080/routes/yourRouteId^{Image Removed} and it default present the route in XML.
Camel uses JAXB to process the XML route definitions.

...