OSGI-INF.blueprint.camel-log.xml Maven / Gradle / Ivy
<?xml version="1.0"?> <!-- Copyright 2005-2014 Red Hat, Inc. Red Hat licenses this file to you under the Apache License, version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- The root element for any OSGi Blueprint file is 'blueprint' - you also see the namespace definitions for both the Blueprint and the Camel namespaces. --> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd"> <!-- The namespace for the camelContext element in Blueprint is 'http://camel.apache.org/schema/blueprint'. While it is not required to assign id's to the <camelContext/> and <route/> elements, it is a good idea to set those for runtime management purposes (logging, JMX MBeans, ...) --> <camelContext id="log-wiki-example-context" xmlns="http://camel.apache.org/schema/blueprint" > <!-- A very simple Camel route, that uses a timer to trigger a message every 5 second. The <setBody> sets a body into the Camel Message. The <log/> elements are used to add human-friendly business logging statements. They make it easier to see what the route is doing. --> <route id="log-wiki-route"> <from uri="timer:foo?period=5s"/> <setBody> <simple>Hello from Fabric based Camel route!</simple> </setBody> <log message=">>> ${body} : ${sys.runtime.id}"/> </route> </camelContext> </blueprint>
© 2015 - 2025 Weber Informatics LLC | Privacy Policy