You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by zr...@apache.org on 2019/08/12 10:50:14 UTC
[camel] branch master updated: CAMEL-13800: fix some issues in
mobile resolutions
This is an automated email from the ASF dual-hosted git repository.
zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new b6208d8 CAMEL-13800: fix some issues in mobile resolutions
b6208d8 is described below
commit b6208d8fa9a017bf0edd3d1b3d88e0ef785a0f16
Author: Zoran Regvart <zr...@apache.org>
AuthorDate: Mon Aug 12 12:49:59 2019 +0200
CAMEL-13800: fix some issues in mobile resolutions
We have some text, notably section headings with long titles, that
cannot be broken into several rows. The default behavior in such cases
for many low resolution mobile browsers is to zoom out and while doing
that the text size is unreadable. This tries to reword some of the text
so it can be broken into multiple rows preventing this zoom out.
---
components/camel-ftp/src/main/docs/ftp-component.adoc | 6 +++---
.../src/main/docs/google-calendar-stream-component.adoc | 2 +-
components/camel-http/src/main/docs/http-component.adoc | 4 ++--
.../src/main/docs/micrometer-component.adoc | 14 +++++++-------
components/camel-sql/src/main/docs/sql-component.adoc | 2 +-
docs/components/modules/ROOT/pages/ftp-component.adoc | 6 +++---
.../ROOT/pages/google-calendar-stream-component.adoc | 2 +-
docs/components/modules/ROOT/pages/http-component.adoc | 4 ++--
.../modules/ROOT/pages/micrometer-component.adoc | 14 +++++++-------
docs/components/modules/ROOT/pages/sql-component.adoc | 2 +-
10 files changed, 28 insertions(+), 28 deletions(-)
diff --git a/components/camel-ftp/src/main/docs/ftp-component.adoc b/components/camel-ftp/src/main/docs/ftp-component.adoc
index c4a831c..7dd8c56 100644
--- a/components/camel-ftp/src/main/docs/ftp-component.adoc
+++ b/components/camel-ftp/src/main/docs/ftp-component.adoc
@@ -485,7 +485,7 @@ FTP server we need to traverse and download files:
And that we have a file in each of sub-a (a.txt) and sub-b (b.txt)
folder.
-==== Using stepwise=true (default mode)
+== Using stepwise=true (default mode)
[source,java]
----
@@ -575,7 +575,7 @@ disconnected.
As you can see when stepwise is enabled, it will traverse the directory
structure using CD xxx.
-==== Using stepwise=false
+== Using stepwise=false
[source,java]
----
@@ -656,7 +656,7 @@ from("ftps://admin@localhost:2222/public/camel?password=admin&ftpClient.trustSto
.to("bean:foo");
----
-== Filter using `org.apache.camel.component.file.GenericFileFilter`
+== Custom filtering
Camel supports pluggable filtering strategies. This strategy it to use
the build in `org.apache.camel.component.file.GenericFileFilter` in
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
index 016b43b..92464a6 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
@@ -40,7 +40,7 @@ The Google Calendar Component uses the following URI format:
--------------------------------------------------------
-== GoogleCalendarStreamComponent
+== Google Calendar stream component options
// component options: START
diff --git a/components/camel-http/src/main/docs/http-component.adoc b/components/camel-http/src/main/docs/http-component.adoc
index f6ddcf5..ea7ae44 100644
--- a/components/camel-http/src/main/docs/http-component.adoc
+++ b/components/camel-http/src/main/docs/http-component.adoc
@@ -295,9 +295,9 @@ the `HttpOperationFailedException` from being thrown for failed response
codes. This allows you to get any response from the remote server. +
There is a sample below demonstrating this.
-== HttpOperationFailedException
+== Exceptions
-This exception contains the following information:
+`HttpOperationFailedException` exception contains the following information:
* The HTTP status code
* The HTTP status line (text of the status code)
diff --git a/components/camel-micrometer/src/main/docs/micrometer-component.adoc b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
index fa86a27..9ee43ee 100644
--- a/components/camel-micrometer/src/main/docs/micrometer-component.adoc
+++ b/components/camel-micrometer/src/main/docs/micrometer-component.adoc
@@ -431,9 +431,9 @@ from("direct:in")
----
-== MicrometerRoutePolicyFactory
+== Using Micrometer route policy factory
-This factory allows to add a RoutePolicy for each
+`MicrometerRoutePolicyFactory` allows to add a RoutePolicy for each
route in order to exposes route utilization statistics using Micrometer.
This factory can be used in Java and XML as the examples below
demonstrates.
@@ -472,9 +472,9 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerRoutePolicy`.
-== MicrometerMessageHistoryFactory
+== Using Micrometer message history factory
-This factory allows to use metrics to capture Message History performance
+`MicrometerMessageHistoryFactory` allows to use metrics to capture Message History performance
statistics while routing messages. It works by using a Micrometer Timer for
each node in all the routes. This factory can be used in Java and XML as
the examples below demonstrates.
@@ -520,7 +520,7 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerMessageHistory`.
-== MicrometerEventNotifiers
+== Micrometer event notification
There is a `MicrometerRouteEventNotifier` (counting added and running routes) and a
`MicrometerExchangeEventNotifier` (timing exchanges from their creation to their completion).
@@ -548,9 +548,9 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerEventNotifier`.
-== InstrumentedThreadPoolFactory
+== Instrumenting Camel thread pools
-This factory allows you to gather performance information about Camel Thread Pools by injecting a `InstrumentedThreadPoolFactory`
+`InstrumentedThreadPoolFactory` allows you to gather performance information about Camel Thread Pools by injecting a `InstrumentedThreadPoolFactory`
which collects information from inside of Camel.
See more details at Advanced configuration of CamelContext using Spring.
diff --git a/components/camel-sql/src/main/docs/sql-component.adoc b/components/camel-sql/src/main/docs/sql-component.adoc
index f41f87f..372bfca 100644
--- a/components/camel-sql/src/main/docs/sql-component.adoc
+++ b/components/camel-sql/src/main/docs/sql-component.adoc
@@ -538,7 +538,7 @@ does not map to any of the JDBC time types: *DATE*, *TIME*, or
When working with concurrent consumers it is crucial to create a unique constraint on the columns processorName and messageId.
Because the syntax for this constraint differs from database to database, we do not show it here.
-=== Customize the JdbcMessageIdRepository
+=== Customize the JDBC idempotency repository
You have a few options to tune the
`org.apache.camel.processor.idempotent.jdbc.JdbcMessageIdRepository` for
diff --git a/docs/components/modules/ROOT/pages/ftp-component.adoc b/docs/components/modules/ROOT/pages/ftp-component.adoc
index c4a831c..7dd8c56 100644
--- a/docs/components/modules/ROOT/pages/ftp-component.adoc
+++ b/docs/components/modules/ROOT/pages/ftp-component.adoc
@@ -485,7 +485,7 @@ FTP server we need to traverse and download files:
And that we have a file in each of sub-a (a.txt) and sub-b (b.txt)
folder.
-==== Using stepwise=true (default mode)
+== Using stepwise=true (default mode)
[source,java]
----
@@ -575,7 +575,7 @@ disconnected.
As you can see when stepwise is enabled, it will traverse the directory
structure using CD xxx.
-==== Using stepwise=false
+== Using stepwise=false
[source,java]
----
@@ -656,7 +656,7 @@ from("ftps://admin@localhost:2222/public/camel?password=admin&ftpClient.trustSto
.to("bean:foo");
----
-== Filter using `org.apache.camel.component.file.GenericFileFilter`
+== Custom filtering
Camel supports pluggable filtering strategies. This strategy it to use
the build in `org.apache.camel.component.file.GenericFileFilter` in
diff --git a/docs/components/modules/ROOT/pages/google-calendar-stream-component.adoc b/docs/components/modules/ROOT/pages/google-calendar-stream-component.adoc
index 016b43b..92464a6 100644
--- a/docs/components/modules/ROOT/pages/google-calendar-stream-component.adoc
+++ b/docs/components/modules/ROOT/pages/google-calendar-stream-component.adoc
@@ -40,7 +40,7 @@ The Google Calendar Component uses the following URI format:
--------------------------------------------------------
-== GoogleCalendarStreamComponent
+== Google Calendar stream component options
// component options: START
diff --git a/docs/components/modules/ROOT/pages/http-component.adoc b/docs/components/modules/ROOT/pages/http-component.adoc
index f6ddcf5..ea7ae44 100644
--- a/docs/components/modules/ROOT/pages/http-component.adoc
+++ b/docs/components/modules/ROOT/pages/http-component.adoc
@@ -295,9 +295,9 @@ the `HttpOperationFailedException` from being thrown for failed response
codes. This allows you to get any response from the remote server. +
There is a sample below demonstrating this.
-== HttpOperationFailedException
+== Exceptions
-This exception contains the following information:
+`HttpOperationFailedException` exception contains the following information:
* The HTTP status code
* The HTTP status line (text of the status code)
diff --git a/docs/components/modules/ROOT/pages/micrometer-component.adoc b/docs/components/modules/ROOT/pages/micrometer-component.adoc
index fa86a27..9ee43ee 100644
--- a/docs/components/modules/ROOT/pages/micrometer-component.adoc
+++ b/docs/components/modules/ROOT/pages/micrometer-component.adoc
@@ -431,9 +431,9 @@ from("direct:in")
----
-== MicrometerRoutePolicyFactory
+== Using Micrometer route policy factory
-This factory allows to add a RoutePolicy for each
+`MicrometerRoutePolicyFactory` allows to add a RoutePolicy for each
route in order to exposes route utilization statistics using Micrometer.
This factory can be used in Java and XML as the examples below
demonstrates.
@@ -472,9 +472,9 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerRoutePolicy`.
-== MicrometerMessageHistoryFactory
+== Using Micrometer message history factory
-This factory allows to use metrics to capture Message History performance
+`MicrometerMessageHistoryFactory` allows to use metrics to capture Message History performance
statistics while routing messages. It works by using a Micrometer Timer for
each node in all the routes. This factory can be used in Java and XML as
the examples below demonstrates.
@@ -520,7 +520,7 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerMessageHistory`.
-== MicrometerEventNotifiers
+== Micrometer event notification
There is a `MicrometerRouteEventNotifier` (counting added and running routes) and a
`MicrometerExchangeEventNotifier` (timing exchanges from their creation to their completion).
@@ -548,9 +548,9 @@ If JMX is enabled in the CamelContext, the MBean is registered in the `type=serv
with `name=MicrometerEventNotifier`.
-== InstrumentedThreadPoolFactory
+== Instrumenting Camel thread pools
-This factory allows you to gather performance information about Camel Thread Pools by injecting a `InstrumentedThreadPoolFactory`
+`InstrumentedThreadPoolFactory` allows you to gather performance information about Camel Thread Pools by injecting a `InstrumentedThreadPoolFactory`
which collects information from inside of Camel.
See more details at Advanced configuration of CamelContext using Spring.
diff --git a/docs/components/modules/ROOT/pages/sql-component.adoc b/docs/components/modules/ROOT/pages/sql-component.adoc
index f41f87f..372bfca 100644
--- a/docs/components/modules/ROOT/pages/sql-component.adoc
+++ b/docs/components/modules/ROOT/pages/sql-component.adoc
@@ -538,7 +538,7 @@ does not map to any of the JDBC time types: *DATE*, *TIME*, or
When working with concurrent consumers it is crucial to create a unique constraint on the columns processorName and messageId.
Because the syntax for this constraint differs from database to database, we do not show it here.
-=== Customize the JdbcMessageIdRepository
+=== Customize the JDBC idempotency repository
You have a few options to tune the
`org.apache.camel.processor.idempotent.jdbc.JdbcMessageIdRepository` for