[
https://issues.apache.org/activemq/browse/CAMEL-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Tam updated CAMEL-1203:
-------------------------------
Attachment: CAMEL-1203.patch
I polished up the patch a bit. Please have a look to make sure I didn't mess
up something. Here is some highlights. (and yes, we will create a wiki page.)
* named "restlet" more consistently throughout to avoid name
clashing/confusion with the rest component.
* removed hardcoded http protocol in the component (although only http has
been tested). the protocol is read from the uri (as the next bullet).
* made the uri work like jetty component in that users can specfy a uri like
"restlet:http://<host>/<resource>". I removed the default internal server
that implicitly started on 8080. Instead, it starts a server based on the
scheme/host/port from the uri for the consumer. Like the jetty http consumer,
the host probably should be localhost/0.0.0.0.
* allowed binding to be looked up from registry. The restletBindingRef query
from uri specifies that entry name to lookup.
* used the restletMethod query in the uri to specify http method. Both
"restletBindingRef" and "restletMethod" are excluded from the uri used in the
restlet request.
> REST (Restlet based) component
> ------------------------------
>
> Key: CAMEL-1203
> URL: https://issues.apache.org/activemq/browse/CAMEL-1203
> Project: Apache Camel
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Przemyslaw Budzik
> Assignee: William Tam
> Attachments: CAMEL-1203.patch, camel-restlet.patch
>
>
> This is the code I was talking with James which we are using in SubRecord. It
> is minimalistic, but does its job for both consumer and producer and is very
> easy to use. If you want could be a replacement for the current camel-rest
> (or could be merged).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
