My standalone camel app stops routing when I simulate daylight saving time
change by setting the system time back an hour (e.g. date --set "2013-10-16
00:00:30"). Once the system time catches up again to where the time was when
it was set back an hour, the routes all start going again.
I'm using
yes,
from your email that you have used to create your nabble login, send an
email to users@camel.apache.org with the subject subscribe
--
View this message in context:
http://camel.465427.n5.nabble.com/Being-able-to-post-and-reveice-email-notification-to-subscribed-posts-tp5741693p5741695.h
ok, try not putting anything in the subject.
--
View this message in context:
http://camel.465427.n5.nabble.com/Being-able-to-post-and-reveice-email-notification-to-subscribed-posts-tp5741693p5741698.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I'm using Camel 2.12 and have a standalone Camel instance.
One of the routes is an http endpoint that expects a post body containing a
SOAP envelope that then needs to unmarshall the soap, marshall it into Json
and hand it off to another endpoint that expects Json:
ServiceInterfaceStrategy strate
I have a readonly source for a file consumer so I'm using noop true which
gets me idempotent in memory store. However sometimes they will redrop an
update with the same name. Please direct me to how to modify the idempotent
store to account for filename and timestamp. Or is there a better way?
Str
How can I flush the idempotent inmemory cache without restarting my camel
service?
--
View this message in context:
http://camel.465427.n5.nabble.com/how-to-flush-idempotent-in-memory-cache-tp5764024.html
Sent from the Camel - Users mailing list archive at Nabble.com.
perhaps a new salesforce field "is_readonly" is needed in LoginToken to fix
the DTO generator?
[INFO] --- camel-salesforce-maven-plugin:2.15.3:generate (default-cli) @
salesforceIntegration ---
[DEBUG] Dependency collection stats: {ConflictMarker.analyzeTime=0,
ConflictMarker.markTime=0, Conflict
My standalone camel instance needs a salesforce component. It has:
public class Driver
{
private Main main;
static final Logger log = LoggerFactory.getLogger(Driver.class);
public void startDriver() throws Exception
{
main = new Main();
Yes, I am referencing the tests. They don't include how to make it work in a
standalone camel. The question is how to get the instance of
SalesforceComponent in the CamelContext of the instance of standalone
org.apache.camel.main.Main. So i've done it in my RouteBuilder configure()
where i can add
it's not getting the salesforce component into the camel context
--
View this message in context:
http://camel.465427.n5.nabble.com/how-to-get-loginConfig-into-standalone-camel-salesforce-component-tp5771694p5771878.html
Sent from the Camel - Users mailing list archive at Nabble.com.
It's working with a lazy init of the salesforce component in the route. I
couldn't get the camel context to recognize that the component was added in
main or in the route builder, but it works from a processor in the route. In
the processor the component has to be created with the camel context fro
11 matches
Mail list logo
