Author: buildbot
Date: Wed Sep 17 13:17:53 2014
New Revision: 922521
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/optaplanner.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/optaplanner.html
==============================================================================
--- websites/production/camel/content/optaplanner.html (original)
+++ websites/production/camel/content/optaplanner.html Wed Sep 17 13:17:53 2014
@@ -85,92 +85,37 @@
<tbody>
<tr>
<td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="OptaPlanner-OptaPlanner">OptaPlanner</h2>
-<p><strong>Available as of Camel 2.13</strong></p>
-
-<p>The <strong>optaplanner:</strong> component solves the planning problem
contained in a message with <a shape="rect" class="external-link" href="http://www.optaplanner.org/"
rel="nofollow">OptaPlanner</a>.<br clear="none">
-For example: feed it an unsolved Vehicle Routing problem and it solves it.</p>
-
-<p>Maven users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p>
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<dependency>
+<div class="wiki-content maincontent"><h2 id="OptaPlanner-OptaPlanner">OptaPlanner</h2><p><strong>Available
as of Camel 2.13</strong></p><p>The <strong>optaplanner:</strong>
component solves the planning problem contained in a message with <a shape="rect" class="external-link"
href="http://www.optaplanner.org/" rel="nofollow">OptaPlanner</a>.<br clear="none">
For example: feed it an unsolved Vehicle Routing problem and it solves it.</p><p>Maven
users will need to add the following dependency to their <code>pom.xml</code>
for this component:</p><div class="code panel pdl" style="border-width: 1px;"><div
class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-optaplanner</artifactId>
<version>x.x.x</version><!-- use the same version
as your Camel core version -->
</dependency>
]]></script>
-</div></div>
-
-<h3 id="OptaPlanner-URIformat">URI format</h3>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-optaplanner:solverConfig[?options]
+</div></div><h3 id="OptaPlanner-URIformat">URI format</h3><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[optaplanner:solverConfig[?options]
]]></script>
-</div></div>
-<p>The <strong>solverConfig</strong> is the classpath-local URI of the
solverConfig, for example <code>/org/foo/barSolverConfig.xml</code>.</p>
-
-<p>You can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p>
-
-<h3 id="OptaPlanner-Options">Options</h3>
-
-<p>No options supported yet.</p>
-
-<h3 id="OptaPlanner-MessageHeaders">Message Headers</h3>
-
-<p>No message headers supported yet.</p>
-
-<h3 id="OptaPlanner-MessageBody">Message Body</h3>
-
-<p>Camel takes the planning problem for the IN body, solves it and returns it on the
OUT body.<br clear="none">
-The IN body object must implement the optaplanner interface <code>Solution</code>.</p>
-
-<h3 id="OptaPlanner-Termination">Termination</h3>
-
-<p>The solving will take as long as specified in the <code>solverConfig</code>.</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[
-<solver>
+</div></div><p>The <strong>solverConfig</strong> is the classpath-local
URI of the solverConfig, for example <code>/org/foo/barSolverConfig.xml</code>.</p><p>You
can append query options to the URI in the following format, <code>?option=value&option=value&...</code></p><h3
id="OptaPlanner-Options">Options</h3><p>No options supported yet.</p><h3
id="OptaPlanner-MessageHeaders">Message Headers</h3><p>No message headers supported
yet.</p><h3 id="OptaPlanner-MessageBody">Message Body</h3><p>Camel
takes the planning problem for the IN body, solves it and returns it on the OUT body.<br
clear="none"> The IN body object must implement the optaplanner interface <code>Solution</code>.</p><h3
id="OptaPlanner-Termination">Termination</h3><p>The solving will take as long
as specified in the <code>solverConfig</code>.</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: xml; gutter: false" type="syntaxhighlighter"><![CDATA[<solver>
...
<termination>
<!-- Terminate after 10 seconds, unless it's not feasible by then yet
-->
<terminationCompositionStyle>AND</terminationCompositionStyle>
- <maximumSecondsSpend>10</maximumSecondsSpend>
- <scoreAttained>-1hard/0soft</scoreAttained>
+ <secondsSpentLimit>10</secondsSpentLimit>
+ <bestScoreLimit>-1hard/0soft</bestScoreLimit>
</termination>
...
<solver>
]]></script>
-</div></div>
-
-<p><strong>NOTE</strong> While the Solver is solving, it will effectively
hog that camel thread. Future improvements might include solving in a separate thread:</p>
-<ul class="alternate"><li>Asynchronous solving: 1 request starts the solving
and registers a callback. When the Solver terminates, the best Solution is returned through
the callback.</li><li>2 phase request solving: 1 request starts the solving on
a separate thread. Another request (with an id to the first request) terminates the Solver
with Solver.terminateEarly() and returns the best Solution.</li></ul>
-
-
-<h4 id="OptaPlanner-Samples">Samples</h4>
-
-<p>Solve an planning problem that's on the ActiveMQ queue with OptaPlanner:</p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("activemq:My.Queue").
+</div></div><p><strong>NOTE</strong> While the Solver is solving,
it will effectively hog that camel thread. Future improvements might include solving in a
separate thread:</p><ul class="alternate"><li>Asynchronous solving: 1 request
starts the solving and registers a callback. When the Solver terminates, the best Solution
is returned through the callback.</li><li>2 phase request solving: 1 request starts
the solving on a separate thread. Another request (with an id to the first request) terminates
the Solver with Solver.terminateEarly() and returns the best Solution.</li></ul><h4
id="OptaPlanner-Samples">Samples</h4><p>Solve an planning problem that's on
the ActiveMQ queue with OptaPlanner:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("activemq:My.Queue").
.to("optaplanner:/org/foo/barSolverConfig.xml");
]]></script>
-</div></div>
-
-<p>Expose OptaPlanner as a REST service: </p>
-
-<div class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
-<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[
-from("cxfrs:bean:rsServer?bindingStyle=SimpleConsumer")
+</div></div><p>Expose OptaPlanner as a REST service:</p><div class="code
panel pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<script class="theme: Default; brush: java; gutter: false" type="syntaxhighlighter"><![CDATA[from("cxfrs:bean:rsServer?bindingStyle=SimpleConsumer")
.to("optaplanner:/org/foo/barSolverConfig.xml");
]]></script>
-</div></div>
-
-
-<h3 id="OptaPlanner-SeeAlso">See Also</h3>
+</div></div><p></p><h3 id="OptaPlanner-SeeAlso">See Also</h3>
<ul><li><a shape="rect" href="configuring-camel.html">Configuring Camel</a></li><li><a
shape="rect" href="component.html">Component</a></li><li><a shape="rect"
href="endpoint.html">Endpoint</a></li><li><a shape="rect" href="getting-started.html">Getting
Started</a></li></ul></div>
</td>
<td valign="top">
|