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 8ed33864447bf1f3b41a47b0951a84d96020e897
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Tue Apr 16 11:02:43 2019 +0200
CAMEL-13422: Remove camel-rmi component
---
components/readme.adoc | 5 +-
docs/components/modules/ROOT/nav.adoc | 1 -
.../modules/ROOT/pages/soapjaxb-dataformat.adoc | 53 +---------------------
3 files changed, 2 insertions(+), 57 deletions(-)
diff --git a/components/readme.adoc b/components/readme.adoc
index b4a23e5..59272a7 100644
--- a/components/readme.adoc
+++ b/components/readme.adoc
@@ -1,7 +1,7 @@
==== Components
// components: START
-Number of Components: 294 in 230 JAR artifacts (0 deprecated)
+Number of Components: 293 in 229 JAR artifacts (0 deprecated)
[width="100%",cols="4,1,5",options="header"]
|===
@@ -700,9 +700,6 @@ Number of Components: 294 in 230 JAR artifacts (0
deprecated)
| link:camel-restlet/src/main/docs/restlet-component.adoc[Restlet]
(camel-restlet) +
`restlet:protocol:host:port/uriPattern` | 2.0 | Component for consuming and
producing Restful resources using Restlet.
-| link:camel-rmi/src/main/docs/rmi-component.adoc[RMI] (camel-rmi) +
-`rmi:hostname:port/name` | 1.0 | The rmi component is for invoking Java RMI
beans from Camel.
-
| link:camel-rss/src/main/docs/rss-component.adoc[RSS] (camel-rss) +
`rss:feedUri` | 2.0 | The rss component is used for consuming RSS feeds.
diff --git a/docs/components/modules/ROOT/nav.adoc
b/docs/components/modules/ROOT/nav.adoc
index 8941f51..4af236b 100644
--- a/docs/components/modules/ROOT/nav.adoc
+++ b/docs/components/modules/ROOT/nav.adoc
@@ -265,7 +265,6 @@
* xref:rest-component.adoc[REST Component]
* xref:restlet-component.adoc[Restlet Component]
* xref:ribbon.adoc[Ribbon Component]
-* xref:rmi-component.adoc[RMI Component]
* xref:rss-component.adoc[RSS Component]
* xref:rss-dataformat.adoc[RSS DataFormat]
* xref:rxjava2.adoc[RxJava2 Component]
diff --git a/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
b/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
index 059e911..9e739c2 100644
--- a/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
+++ b/docs/components/modules/ROOT/pages/soapjaxb-dataformat.adoc
@@ -189,61 +189,10 @@ ServiceInterfaceStrategy strat = new
ServiceInterfaceStrategy(com.example.custo
SoapJaxbDataFormat soapDataFormat = new
SoapJaxbDataFormat("com.example.customerservice.multipart", strat);
-------------------------------------------------------------------------------------------------------------------------------------------
-#### Multi-part Request
-
-The payload parameters for a multi-part request are initiazlied using a
-`BeanInvocation` object that reflects the signature of the target
-operation. The camel-soap DataFormat maps the content in the
-`BeanInvocation` to fields in the SOAP header and body in accordance
-with the JAX-WS mapping when the `marshal()` processor is invoked.
-
-[source,java]
-----------------------------------------------------------------------------------------
-BeanInvocation beanInvocation = new BeanInvocation();
-
-// Identify the target method
-beanInvocation.setMethod(MultiPartCustomerService.class.getMethod("getCustomersByName",
- GetCustomersByName.class,
com.example.customerservice.multipart.Product.class));
-
-// Populate the method arguments
-GetCustomersByName getCustomersByName = new GetCustomersByName();
-getCustomersByName.setName("Dr. Multipart");
-
-Product product = new Product();
-product.setName("Multiuse Product");
-product.setDescription("Useful for lots of things.");
-
-Object[] args = new Object[] {getCustomersByName, product};
-
-// Add the arguments to the bean invocation
-beanInvocation.setArgs(args);
-
-// Set the bean invocation object as the message body
-exchange.getIn().setBody(beanInvocation);
-----------------------------------------------------------------------------------------
-
-#### Multi-part Response
-
-A multi-part soap response may include an element in the soap body and
-will have one or more elements in the soap header. The camel-soap
-DataFormat will unmarshall the element in the soap body (if it exists)
-and place it onto the body of the out message in the exchange. Header
-elements will *not* be marshaled into their JAXB mapped object types.
-Instead, these elements are placed into the camel out message header
-`org.apache.camel.dataformat.soap.UNMARSHALLED_HEADER_LIST`. The
-elements will appear either as element instance values, or as
-JAXBElement values, depending upon the setting for the
-`ignoreJAXBElement` property. This property is inherited from
-camel-jaxb.
-
-You can also have the camel-soap DataFormate ignore header content
-all-together by setting the `ignoreUnmarshalledHeaders` value to `true`.
-
#### Holder Object mapping
JAX-WS specifies the use of a type-parameterized `javax.xml.ws.Holder`
-object for `In/Out` and `Out` parameters. A `Holder` object may be used
-when building the `BeanInvocation`, or you may use an instance of the
+object for `In/Out` and `Out` parameters. You may use an instance of the
parameterized-type directly. The camel-soap DataFormat marshals Holder
values in accordance with the JAXB mapping for the class of the
`Holder`'s value. No mapping is provided for `Holder` objects in an
