camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r888976 - in /websites/production/camel/content: cache/main.pageCache camel-2130-release.html camel-hawtio-maven-goal.html camel-maven-plugin.html
Date Tue, 03 Dec 2013 18:23:00 GMT
Author: buildbot
Date: Tue Dec  3 18:23:00 2013
New Revision: 888976

Log:
Production update by buildbot for camel

Removed:
    websites/production/camel/content/camel-hawtio-maven-goal.html
Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2130-release.html
    websites/production/camel/content/camel-maven-plugin.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/camel-2130-release.html
==============================================================================
--- websites/production/camel/content/camel-2130-release.html (original)
+++ websites/production/camel/content/camel-2130-release.html Tue Dec  3 18:23:00 2013
@@ -94,7 +94,7 @@
 
 <p>Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements
and bug fixes such as...)</p>
 
-<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html"
title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt>
part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>.
Having the hostname in the MBean name does not bring much value, and in fact makes things
more complicated as the mbean name changes depending on the host running Camel.</li><li><a
shape="rect" href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned
up to use simpler naming with symbolicName. Before we could have MBean names with duplicate
bundle ids such as <tt>context=114-114-camel-6</tt>, which now is using the symbolic
name instead, <tt>context=MyApplication</tt>.</li><li>When using multiple
OSGi Blueprint &lt;cm:property-placeholder&gt;'s then Camel now favors using non-default
placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows
for example to define default properties 
 in one placeholder, and override these values in other placeholders.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to download a single
named file without using the FTP LIST command. This allows to download a known file from a
FTP server even when the user account does not have permission to do FTP LIST command.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore file
not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html"
title="Data Format">Data Format</a> using marshal now leverages <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> out of the box
if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory
based.</li><li>Improved using <a shape="rect" href="bean.html" title="Bean">Bean</a>
when the bean is looked up in the <a shape="rect" href="registry.html" title="Registry">Registry</a>,
when using c
 oncurrent processing in the route.</li><li>Added <tt>cache</tt> option
to <tt>beanRef</tt> and <tt>&lt;bean&gt;</tt> in the DSL.
This avoids looking up the <a shape="rect" href="bean.html" title="Bean">Bean</a>
from the <a shape="rect" href="registry.html" title="Registry">Registry</a> on
each usage; this can safely be done for singleton beans.</li><li>Configuring <a
shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in XML
attributes now supports reference lookup using the # syntax, eg <tt>&lt;jaxb xmlStreamWriterWrapper="#myWriterWrapper"
..&gt;</tt></li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a>
component now also support <tt>outputType</tt> to specify the expected output
as either a List or single Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt>
to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect"
href="quartz.html" title="Quartz">Quartz</a> as well as <a shape="rect" href="quartz2.html"

 title="Quartz2">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html"
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to better
support cluster setups (e.g. to not schedule jobs being already scheduled through another
node inside a given cluster).</li><li>Reduced the work the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP does while holding
a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><tt>JndiRegistry</tt>
now implements all the find methods.</li><li><a shape="rect" href="vm.html"
title="VM">VM</a> component now supports <tt>multipleConsumers=true</tt>
across deployment units.</li><li>Added <tt>@PreConsumed</tt> to <a
shape="rect" href="jpa.html" title="JPA">JPA</a> consumer.</li><li>Added
CamelFileName header support to the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a>
producer</li><li>Like as <tt>JpaConsumer</tt> now also <tt>JpaProducer</tt>
of the <a shape
 ="rect" href="jpa.html" title="JPA">JPA</a> component supports the <tt>CamelEntityManager</tt>
header.</li><li><a shape="rect" href="restlet.html" title="Restlet">Restlet</a>
consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect"
href="message.html" title="Message">Message</a>.</li><li><a shape="rect"
href="spring-java-config.html" title="Spring Java Config">Spring Java Config</a>
<tt>CamelConfiguration</tt> now automagically detects all <tt>RouteBuilder</tt>
instances registered in the Spring context if <tt>CamelConfiguration#routes</tt>
method is not overridden.</li><li>Added support for transferring custom headers
with <a shape="rect" href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a
shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream cache
during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now
creates necessary parent directories together with the new repository file.</li><li><a
  shape="rect" href="properties.html" title="Properties">Properties</a> component
and <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property
placeholder</a> will now ignore non existing JVM and environment options as well if
<tt>ignoreMissingLocation</tt> is set to <tt>true</tt>.</li><li>Improved
<a shape="rect" href="stream.html" title="Stream">Stream</a> consumer to enrich
the <a shape="rect" href="message.html" title="Message">Message</a> with headers
about current index / completion flag.</li><li>Added <a shape="rect" href="bean-injection.html"
title="Bean Injection"><tt>@BeanInject</tt></a> to inject beans (obtained
from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) in
your beans such as <tt>RouteBuilder</tt> classes.</li><li>Polished
the <a shape="rect" href="karaf.html" title="Karaf">Karaf</a> commands to output
tables sorted and auto calculated width, so the data is formatted nicely.</li><li>Introduced
<tt>Un
 itOfWorkFactory</tt> to allow end users to use custom <tt>UnitOfWork</tt>
implementations created by the factory.</li><li>Added <tt><a shape="rect"
href="camel-hawtio-maven-goal.html" title="Camel Hawtio Maven Goal">camel:hawtio</a></tt>
Maven goal, as extension to <tt>camel:run</tt> to bootstrap Camel including the
<a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a>
web console.</li><li>Doing request/reply over <a shape="rect" href="jms.html"
title="JMS">JMS</a> allows per individual message <tt>requestTimeout</tt>
value by specifying the timeout value in the <tt>"CamelJmsRequestTimeout"</tt>
header.</li><li><a shape="rect" href="quartz.html" title="Quartz">Quartz</a>
and <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> components
now enlist the quartz scheduler by default in JMX, unless configured to be disabled.</li></ul>
+<ul><li>The MBean names registered by <a shape="rect" href="camel-jmx.html"
title="Camel JMX">Camel JMX</a> no longer include the hostname in the <tt>context</tt>
part, eg before <tt>context=myHost/myCamelId</tt> and now after <tt>context=myCamelId</tt>.
Having the hostname in the MBean name does not bring much value, and in fact makes things
more complicated as the mbean name changes depending on the host running Camel.</li><li><a
shape="rect" href="camel-jmx.html" title="Camel JMX">MBean naming</a> in OSGi cleaned
up to use simpler naming with symbolicName. Before we could have MBean names with duplicate
bundle ids such as <tt>context=114-114-camel-6</tt>, which now is using the symbolic
name instead, <tt>context=MyApplication</tt>.</li><li>When using multiple
OSGi Blueprint &lt;cm:property-placeholder&gt;'s then Camel now favors using non-default
placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows
for example to define default properties 
 in one placeholder, and override these values in other placeholders.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to download a single
named file without using the FTP LIST command. This allows to download a known file from a
FTP server even when the user account does not have permission to do FTP LIST command.</li><li><a
shape="rect" href="ftp2.html" title="FTP2">FTP</a> consumer allow to ignore file
not found or insufficient file permission errors.</li><li><a shape="rect" href="data-format.html"
title="Data Format">Data Format</a> using marshal now leverages <a shape="rect"
href="stream-caching.html" title="Stream caching">Stream caching</a> out of the box
if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory
based.</li><li>Improved using <a shape="rect" href="bean.html" title="Bean">Bean</a>
when the bean is looked up in the <a shape="rect" href="registry.html" title="Registry">Registry</a>,
when using c
 oncurrent processing in the route.</li><li>Added <tt>cache</tt> option
to <tt>beanRef</tt> and <tt>&lt;bean&gt;</tt> in the DSL.
This avoids looking up the <a shape="rect" href="bean.html" title="Bean">Bean</a>
from the <a shape="rect" href="registry.html" title="Registry">Registry</a> on
each usage; this can safely be done for singleton beans.</li><li>Configuring <a
shape="rect" href="data-format.html" title="Data Format">Data Format</a>s in XML
attributes now supports reference lookup using the # syntax, eg <tt>&lt;jaxb xmlStreamWriterWrapper="#myWriterWrapper"
..&gt;</tt></li><li><a shape="rect" href="jdbc.html" title="JDBC">JDBC</a>
component now also support <tt>outputType</tt> to specify the expected output
as either a List or single Object. As well allow to map to a bean using a <tt>BeanRowMapper</tt>
to control the mapping of ROW names to bean properties.</li><li>Both <a shape="rect"
href="quartz.html" title="Quartz">Quartz</a> as well as <a shape="rect" href="quartz2.html"

 title="Quartz2">Quartz2</a> based <a shape="rect" href="scheduledroutepolicy.html"
title="ScheduledRoutePolicy">ScheduledRoutePolicy</a> has been improved to better
support cluster setups (e.g. to not schedule jobs being already scheduled through another
node inside a given cluster).</li><li>Reduced the work the <a shape="rect"
href="aggregator2.html" title="Aggregator2">Aggregate</a> EIP does while holding
a lock during aggregation, which can lead to improved performance in some use-cases.</li><li><tt>JndiRegistry</tt>
now implements all the find methods.</li><li><a shape="rect" href="vm.html"
title="VM">VM</a> component now supports <tt>multipleConsumers=true</tt>
across deployment units.</li><li>Added <tt>@PreConsumed</tt> to <a
shape="rect" href="jpa.html" title="JPA">JPA</a> consumer.</li><li>Added
CamelFileName header support to the <a shape="rect" href="hdfs.html" title="HDFS">HDFS</a>
producer</li><li>Like as <tt>JpaConsumer</tt> now also <tt>JpaProducer</tt>
of the <a shape
 ="rect" href="jpa.html" title="JPA">JPA</a> component supports the <tt>CamelEntityManager</tt>
header.</li><li><a shape="rect" href="restlet.html" title="Restlet">Restlet</a>
consumer now supports returning custom headers as HTTP headers from the Camel <a shape="rect"
href="message.html" title="Message">Message</a>.</li><li><a shape="rect"
href="spring-java-config.html" title="Spring Java Config">Spring Java Config</a>
<tt>CamelConfiguration</tt> now automagically detects all <tt>RouteBuilder</tt>
instances registered in the Spring context if <tt>CamelConfiguration#routes</tt>
method is not overridden.</li><li>Added support for transferring custom headers
with <a shape="rect" href="rabbitmq.html" title="RabbitMQ">RabbitMQ</a> component.</li><li><a
shape="rect" href="crypto.html" title="Crypto">PGPDataFormat</a> enables stream cache
during unmarshaling.</li><li><tt>FileIdempotentRepository</tt> now
creates necessary parent directories together with the new repository file.</li><li><a
  shape="rect" href="properties.html" title="Properties">Properties</a> component
and <a shape="rect" href="using-propertyplaceholder.html" title="Using PropertyPlaceholder">property
placeholder</a> will now ignore non existing JVM and environment options as well if
<tt>ignoreMissingLocation</tt> is set to <tt>true</tt>.</li><li>Improved
<a shape="rect" href="stream.html" title="Stream">Stream</a> consumer to enrich
the <a shape="rect" href="message.html" title="Message">Message</a> with headers
about current index / completion flag.</li><li>Added <a shape="rect" href="bean-injection.html"
title="Bean Injection"><tt>@BeanInject</tt></a> to inject beans (obtained
from the <a shape="rect" href="registry.html" title="Registry">Registry</a>) in
your beans such as <tt>RouteBuilder</tt> classes.</li><li>Polished
the <a shape="rect" href="karaf.html" title="Karaf">Karaf</a> commands to output
tables sorted and auto calculated width, so the data is formatted nicely.</li><li>Introduced
<tt>Un
 itOfWorkFactory</tt> to allow end users to use custom <tt>UnitOfWork</tt>
implementations created by the factory.</li><li>Doing request/reply over <a
shape="rect" href="jms.html" title="JMS">JMS</a> allows per individual message <tt>requestTimeout</tt>
value by specifying the timeout value in the <tt>"CamelJmsRequestTimeout"</tt>
header.</li><li><a shape="rect" href="quartz.html" title="Quartz">Quartz</a>
and <a shape="rect" href="quartz2.html" title="Quartz2">Quartz2</a> components
now enlist the quartz scheduler by default in JMX, unless configured to be disabled.</li></ul>
 
 
 
@@ -135,7 +135,7 @@
 
 <h3><a shape="rect" name="Camel2.13.0Release-NewTooling"></a>New Tooling</h3>
 
-<ul><li><tt><a shape="rect" href="camel-hawtio-maven-goal.html" title="Camel
Hawtio Maven Goal">camel:hawtio</a></tt> Maven goal.</li></ul>
+<ul><li><tt><span class="error">[camel:hawtio]</span></tt>
Maven goal.</li></ul>
 
 
 <h2><a shape="rect" name="Camel2.13.0Release-APIchanges"></a>API changes</h2>

Modified: websites/production/camel/content/camel-maven-plugin.html
==============================================================================
--- websites/production/camel/content/camel-maven-plugin.html (original)
+++ websites/production/camel/content/camel-maven-plugin.html Tue Dec  3 18:23:00 2013
@@ -92,7 +92,7 @@
 <h3><a shape="rect" name="CamelMavenPlugin-GoalsSupported"></a>Goals Supported</h3>
 
 <div class="table-wrap">
-<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Documentation </th><th colspan="1" rowspan="1" class="confluenceTh">
Goal </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="camel-run-maven-goal.html"
title="Camel Run Maven Goal">camel:run</a> </td><td colspan="1" rowspan="1"
class="confluenceTd"> camel:run </td><td colspan="1" rowspan="1" class="confluenceTd">
Boots up Camel in the context of a separately initiated Java thread using the <a shape="rect"
href="spring.html" title="Spring">Spring</a> configuration at <b>META-INF/spring/*.xml</b>
and runs your routing rules. From Camel 2.10 onwards also OSGi blueprint is supported to load
from <b>OSGI-INF/blueprint/*.xml</b> (requires to configure the plugin to use
blueprint). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<a shape="rect" href="camel-hawtio-maven-goal.html" tit
 le="Camel Hawtio Maven Goal">camel:hawtio</a> </td><td colspan="1" rowspan="1"
class="confluenceTd"> camel:hawtio </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>Camel 2.13/2.12.3:</b> Extension to camel:run goal, to run Camel including
the <a shape="rect" class="external-link" href="http://hawt.io/" rel="nofollow">hawtio</a>
web console at <tt>http:localhost:8080/hawtio</tt>, allowing users to visualize
their running Camel applications, debug and profile routes, and much more. </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="camel-embedded-maven-goal.html"
title="Camel Embedded Maven Goal">camel:embedded</a> </td><td colspan="1"
rowspan="1" class="confluenceTd"> camel:embedded </td><td colspan="1" rowspan="1"
class="confluenceTd"> Boots up Camel using the <a shape="rect" href="spring.html" title="Spring">Spring</a>
configuration at <b>META-INF/spring/*.xml</b> and runs your routing rules. From
Camel 2.10 onwards also OSGi blueprint is 
 supported to load from <b>OSGI-INF/blueprint/*.xml</b> (requires to configure
the plugin to use blueprint). </td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"> <a shape="rect" href="camel-dot-maven-goal.html" title="Camel
Dot Maven Goal">camel:dot</a> </td><td colspan="1" rowspan="1" class="confluenceTd">
camel:dot </td><td colspan="1" rowspan="1" class="confluenceTd"> <b>deprecated</b>:
Generates DOT files and then HTML, PNG, SVG files for your EIP routing rules with integration
into Maven Reports. This plugin <b>only</b> supports Spring XML files. </td></tr></tbody></table>
+<table class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1"
class="confluenceTh"> Documentation </th><th colspan="1" rowspan="1" class="confluenceTh">
Goal </th><th colspan="1" rowspan="1" class="confluenceTh"> Description </th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="camel-run-maven-goal.html"
title="Camel Run Maven Goal">camel:run</a> </td><td colspan="1" rowspan="1"
class="confluenceTd"> camel:run </td><td colspan="1" rowspan="1" class="confluenceTd">
Boots up Camel in the context of a separately initiated Java thread using the <a shape="rect"
href="spring.html" title="Spring">Spring</a> configuration at <b>META-INF/spring/*.xml</b>
and runs your routing rules. From Camel 2.10 onwards also OSGi blueprint is supported to load
from <b>OSGI-INF/blueprint/*.xml</b> (requires to configure the plugin to use
blueprint). </td></tr><tr><td colspan="1" rowspan="1" class="confluenceTd">
<a shape="rect" href="camel-embedded-maven-goal.html" t
 itle="Camel Embedded Maven Goal">camel:embedded</a> </td><td colspan="1"
rowspan="1" class="confluenceTd"> camel:embedded </td><td colspan="1" rowspan="1"
class="confluenceTd"> Boots up Camel using the <a shape="rect" href="spring.html" title="Spring">Spring</a>
configuration at <b>META-INF/spring/*.xml</b> and runs your routing rules. From
Camel 2.10 onwards also OSGi blueprint is supported to load from <b>OSGI-INF/blueprint/*.xml</b>
(requires to configure the plugin to use blueprint). </td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"> <a shape="rect" href="camel-dot-maven-goal.html"
title="Camel Dot Maven Goal">camel:dot</a> </td><td colspan="1" rowspan="1"
class="confluenceTd"> camel:dot </td><td colspan="1" rowspan="1" class="confluenceTd">
<b>deprecated</b>: Generates DOT files and then HTML, PNG, SVG files for your
EIP routing rules with integration into Maven Reports. This plugin <b>only</b>
supports Spring XML files. </td></tr></tbody></table>
 </div>
 
 



Mime
View raw message