You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/04/17 09:41:31 UTC
[camel] 14/38: CAMEL-13422: Remove camel-rmi component
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch mock
in repository https://gitbox.apache.org/repos/asf/camel.git
commit f5719b6c50a3ab67e5436e37e39688418804ba85
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Tue Apr 16 10:25:52 2019 +0200
CAMEL-13422: Remove camel-rmi component
---
apache-camel/pom.xml | 10 --
bom/camel-bom/pom.xml | 10 --
.../modules/ROOT/pages/rmi-component.adoc | 159 ---------------------
...-extra-camel-componets-in-servicemix-camel.adoc | 73 ----------
.../camel-spring-boot-dependencies/pom.xml | 10 --
5 files changed, 262 deletions(-)
diff --git a/apache-camel/pom.xml b/apache-camel/pom.xml
index d7d8293..f34eb63 100644
--- a/apache-camel/pom.xml
+++ b/apache-camel/pom.xml
@@ -1153,11 +1153,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
<artifactId>camel-rss</artifactId>
<version>${project.version}</version>
</dependency>
@@ -2602,11 +2597,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi-starter</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
<artifactId>camel-rss-starter</artifactId>
<version>${project.version}</version>
</dependency>
diff --git a/bom/camel-bom/pom.xml b/bom/camel-bom/pom.xml
index a0821f4..c3c6265 100644
--- a/bom/camel-bom/pom.xml
+++ b/bom/camel-bom/pom.xml
@@ -2215,16 +2215,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi-starter</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
<artifactId>camel-rss</artifactId>
<version>${project.version}</version>
</dependency>
diff --git a/docs/components/modules/ROOT/pages/rmi-component.adoc b/docs/components/modules/ROOT/pages/rmi-component.adoc
deleted file mode 100644
index 36b1974..0000000
--- a/docs/components/modules/ROOT/pages/rmi-component.adoc
+++ /dev/null
@@ -1,159 +0,0 @@
-[[rmi-component]]
-== RMI Component
-
-*Available as of Camel version 1.0*
-
-The *rmi:* component binds Exchanges to the RMI
-protocol (JRMP).
-
-Since this binding is just using RMI, normal RMI rules still apply
-regarding what methods can be invoked. This component supports only
-Exchanges that carry a method invocation from an interface that extends
-the http://java.sun.com/j2se/1.3/docs/api/java/rmi/Remote.html[Remote]
-interface. All parameters in the method should be either
-http://java.sun.com/j2se/1.5.0/docs/api/java/io/Serializable.html[Serializable]
-or `Remote` objects.
-
-Maven users will need to add the following dependency to their `pom.xml`
-for this component:
-
-[source,xml]
-------------------------------------------------------------
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-------------------------------------------------------------
-
-### URI format
-
-[source,java]
-------------------------------------------------------------------
-rmi://rmi-regisitry-host:rmi-registry-port/registry-path[?options]
-------------------------------------------------------------------
-
-For example:
-
-[source,java]
-------------------------------------
-rmi://localhost:1099/path/to/service
-------------------------------------
-
-You can append query options to the URI in the following format,
-`?option=value&option=value&...`
-
-### Options
-
-
-// component options: START
-The RMI component has no options.
-// component options: END
-
-
-
-// endpoint options: START
-The RMI endpoint is configured using URI syntax:
-
-----
-rmi:hostname:port/name
-----
-
-with the following path and query parameters:
-
-==== Path Parameters (3 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *hostname* | Hostname of RMI server | localhost | String
-| *name* | *Required* Name to use when binding to RMI server | | String
-| *port* | Port number of RMI server | 1099 | int
-|===
-
-
-==== Query Parameters (6 parameters):
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *method* (common) | You can set the name of the method to invoke. | | String
-| *remoteInterfaces* (common) | To specific the remote interfaces. | | List
-| *bridgeErrorHandler* (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean
-| *exceptionHandler* (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | | ExceptionHandler
-| *exchangePattern* (consumer) | Sets the exchange pattern when the consumer creates an exchange. | | ExchangePattern
-| *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean
-|===
-// endpoint options: END
-// spring-boot-auto-configure options: START
-=== Spring Boot Auto-Configuration
-
-When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
-
-[source,xml]
-----
-<dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi-starter</artifactId>
- <version>x.x.x</version>
- <!-- use the same version as your Camel core version -->
-</dependency>
-----
-
-
-The component supports 2 options, which are listed below.
-
-
-
-[width="100%",cols="2,5,^1,2",options="header"]
-|===
-| Name | Description | Default | Type
-| *camel.component.rmi.enabled* | Enable rmi component | true | Boolean
-| *camel.component.rmi.resolve-property-placeholders* | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | Boolean
-|===
-// spring-boot-auto-configure options: END
-
-
-
-### Using
-
-To call out to an existing RMI service registered in an RMI registry,
-create a route similar to the following:
-
-[source,java]
-------------------------------------------------
-from("pojo:foo").to("rmi://localhost:1099/foo");
-------------------------------------------------
-
-To bind an existing camel processor or service in an RMI registry,
-define an RMI endpoint as follows:
-
-[source,java]
--------------------------------------------------------------------------
-RmiEndpoint endpoint= (RmiEndpoint) endpoint("rmi://localhost:1099/bar");
-endpoint.setRemoteInterfaces(ISay.class);
-from(endpoint).to("pojo:bar");
--------------------------------------------------------------------------
-
-Note that when binding an RMI consumer endpoint, you must specify the
-`Remote` interfaces exposed.
-
-In XML DSL you can do as follows from *Camel 2.7* onwards:
-
-[source,xml]
-------------------------------------------------------------------------------------------------------------------------
- <camel:route>
- <from uri="rmi://localhost:37541/helloServiceBean?remoteInterfaces=org.apache.camel.example.osgi.HelloService"/>
- <to uri="bean:helloServiceBean"/>
- </camel:route>
-------------------------------------------------------------------------------------------------------------------------
-
-### See Also
-
-* Configuring Camel
-* Component
-* Endpoint
-* Getting Started
diff --git a/docs/user-manual/en/faq/how-to-use-extra-camel-componets-in-servicemix-camel.adoc b/docs/user-manual/en/faq/how-to-use-extra-camel-componets-in-servicemix-camel.adoc
deleted file mode 100644
index f397263..0000000
--- a/docs/user-manual/en/faq/how-to-use-extra-camel-componets-in-servicemix-camel.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-[[HowtouseextraCamelcomponetsinservicemixcamel-HowtouseextraCamelcomponetsinservicemixcamel]]
-=== How to use extra Camel componets in servicemix-camel?
-
-Since ServiceMix 3's component has same hierarchies of the class loaders
-with the J2EE application server, and the components the class loader is
-separated with the SU's. And Camel has lots of components, we just
-include the camel-core and camel-spring components in the
-servicemix-camel by default. When the user want to use other camel
-component, they always add the camel-xxx component into their SU lib.
-In this way if there is a class which is loaded from the different SU
-classloader and registed into the camel-core's registry by
-servicemix-camel component , we will faced on the typical class cast
-exception in Servicemix3. Basically this exception is caused by the same
-class is loaded by different class loader.
-
-You may meet an issue of the class cast exception when deploying the
-same servicemix-camel component SU twice.
-
-In this case, when the SU is redeployed, it will create a new deployer
-which will create an application context with the class loader of
-servicemix-camel component, and then using the SU's class loader to
-create a camel context.
-Since the SU is redeployed, Servicemix will create a new class loader to
-load the SU's lib jars and resources.
-When the SU initial the rmi component, boom , we meet the situation of
-same component loaded with different class loader, The class cast
-exception is thrown out.
-
-Note, in Servicemix4's camel component, we will not get that kind of
-issue, since the OSGi will help us to manage the relationship of the
-jars.
-
-The solution is putting the camel-xxx components and third part jars
-into servicemix-camel component's lib. You need to check out the
-servicemix-camel component's pom.xml and recompile the servicemix-camel
-component by adding the camel-xxx component dependency.
-
-Let me take the latest servicemix-camel as an example:
-
-1. Checking out the servicemix-camel component's pom:
-+
-----
-svn co http://svn.apache.org/repos/asf/servicemix/components/engines/servicemix-camel/trunk/pom.xml
-----
-
-2. If you need camel-rmi component, you just put the dependency into
-the `pom.xml`:
-+
-[source,xml]
-----
-<dependency>
- <groupid>org.apache.camel</groupid>
- <artifactid>camel-rmi</artifactid>
- <version>${camel-version}</version>
-</dependency>
-----
-
-3. Running `mvn install` and copy the `servicemix-camel-*.zip` into the
-deploy directory.
-
-4. Write your servicemix-camel SU, make sure you don't include any
-camel relates jars into the SU's lib, you can use the
-`<scope>provided</scope>` to not packing the artifact.
-+
-[source,xml]
-----
-<dependency>
- <groupid>org.apache.camel</groupid>
- <artifactid>camel-rmi</artifactid>
- <version>${camel-version}</version>
- <scope>provided</scope>
-</dependency>
-----
diff --git a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
index 55415c1..b5eccf9 100644
--- a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
+++ b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
@@ -2430,16 +2430,6 @@
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
- <artifactId>camel-rmi-starter</artifactId>
- <version>${project.version}</version>
- </dependency>
- <dependency>
- <groupId>org.apache.camel</groupId>
<artifactId>camel-rss</artifactId>
<version>${project.version}</version>
</dependency>