Looks like the author of camel-web may be assuming *nix paths.
I'm running this on Windows 7.
Here is the options file that gets generated (and put to
\my_windoze_path\apache-camel-2.14.0\components\camel-web\target\site\apidocs.
Note the mixed path in the --output variable which IMO may be th
Hi,
I tried with the latest Java 8 JDK, 1.8.0_20.
It fails in the same place in exactly the same way.
--
View this message in context:
http://camel.465427.n5.nabble.com/2-14-0-build-fails-on-camel-web-javadocs-tp5756866p5756911.html
Sent from the Camel - Users mailing list archive at Nabbl
Hiya,
I'm compiling 2.14.0 with:
mvn clean install -Pspring4,fastinstall
and getting the following errors below when it hits camel-web.
[Spring4 is the the default now, yes?]
Thanks,
Rick
[INFO]
[INFO] BUILD FAILURE
[IN
Hi,
JSON libraries like Jackson and XStream provide ways of overriding the
serializers/deserializers that get used for various specific object types.
[While you can always hand-annotate code (e.g. with @JsonSerializer) to use
custom serializers and deserializers, that can be cumbersome and invasi
Many (belated) thanks, Claus + Matt.
I think I'm finally getting the fact that the Exchange itself provides an
object with the scope I was seeking (i.e. from when the input message
received by Camel an input transport to when the output message sent from
Camel to the output transport).
[i.e. Ja
Hi Claus,
I'm still a bit confused with precisely how the Camel "bean" tag works and
interacts with Spring prototype beans.
With similar ESB's to Camel, I've seen folks write their own Spring custom
scope such that the same bean is used from when the input message received
by the ESB to when the
Hi
I'm using 2.13.2
The URI option is non-ideal since it sends the credentials in clear text as
part of the http (GET) call.
That's not very secure.
Thanks,
Rick
--
View this message in context:
http://camel.465427.n5.nabble.com/How-can-I-make-a-RecipientList-http-component-use-an-HttpConf
[Sorry, some comments got stripped out of the posting. The first call that
tries to use the HttpComponent fails; the 2nd call that provides basic auth
params in simple-recipientList succeeds.]
Thanks for the reply. I tried your suggestion but it doesn't seem to work
for me.
This:
Hi,
I have a route with two different http calls in it, each with different
security requirements.
How can I configure a recipientList such that it uses an HttpConfiguration
defined elsewhere as shown below?
Namely, here is an example that doesn't recognize the HttpComponent inside
the https bea
Hiya,
I've created a patch for the camel-salesforce component and submitted it as
an attachement for this Jira
https://issues.apache.org/jira/browse/CAMEL-7413?jql=text%20~%20%22camel-salesforce%22
It fixes some configuration issues and documentation bugs.
I'll start tackling some of the meatier
Tremendous, and many thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Java-8-support-and-separately-is-Github-the-best-place-to-submit-code-improvements-tp5754864p5754866.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hiya,
I've just taken the Camel sources from GitHub here:
https://github.com/apache/camel
This seems to be work towards a 2.14-SNAPSHOT release.
Is Java 8 be support planned for 2.14? Spring 4?
Separately, is that github repository above the best place to submit code
improvement ideas? There
The situation is as I outlined in the example. If you're using a component
(like salesforce REST which uses the header and body in some interactions)
to get intermediate results as part of a longer route, that component may
need to control the header and body of the request+response.
I don't see
Yes, that concept is similar to what I've seen done in 2+ places with custom
scopes.
e.g. If you rely heavily on queue transports, you set the request Id for the
scope to be the correllation Id (or Message Id or UUID if you have neither),
and the "route" scope ends when the output message goes to
Hiya,
Yeah, but I think that assumes that components will be thoughtful enough to
pass me what I want back.
If a component (e.g. camel-salesforce) needs both the header and body for me to
make a request-response, I have to hope that it passes me the service bean
instance (that's also in the ex
Hi Michael,
I hear you. The trouble is, sometimes the intermediate transports (e.g. the
Camel Salesforce component) hijack the header and body for their own needs
and you don't have full control over them.
In similar ESBs, I've seen some shops make their own custom Spring message
scope to be the
Hi Claus et al,
I'd like to use a prototype bean in a route such that a new instance gets
created at the beginning of the route, and that same instance is used
throughout the route until the route ends.
Included below are two simple routes and a fragment of a service bean class
that collects part
17 matches
Mail list logo