Acess to the Route's list of RoutePolicies from a custom GenericFileProcessStrategy

[sfbayperson2016]

Hi,
I'm trying implement a custom GenericFileProcessStrategy for an SFTP "from"
endpoint. I figure I just need to write the class then append
"=MyCustomGenericFileProcessStrategy" to the end of the from
uri. Is this correct?

The main question is when GenericFileProcessStrategy.begin() is called I
need to be able to iterate through all the route policies for the route that
the endpoint belongs to, and check if its a specific type of RoutePolicy. Is
this possible from that context? It doesn't look obvious but is there some
way I can do that indirectly through the Endpoint or the Exchange that's
available in that context?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Acess-to-the-Route-s-list-of-RoutePolicies-from-a-custom-GenericFileProcessStrategy-tp5784389.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel route Audit and processing summury

[mabahma]

Thank you for your replay..

I have followd your advice and used the message history EIP
(http://camel.apache.org/message-history.html) and it works perfectly.

But in log that it is giving to me , i have this :

routeid  nodeid  processor  
  
elapsed


route1   to8  *{{url}}*  135


I'have a propertyplaceholder injectd in the context, with a props file
containing the value of url.


Why the value of url wasn't evaluated and replaced by its value? 



the code is as follows :


List list = exchange.getProperty(Exchange.MESSAGE_HISTORY,
List.class);

messageHistory.getNode().getLabel()   --> gives me  {{url}} and not the
real value



How can i have the real value and not just the parameter?

Kind regards,



--
View this message in context: 
http://camel.465427.n5.nabble.com/Re-Camel-route-Audit-and-processing-summury-tp5784339p5784377.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.16 With Log4j2 by DSL

[Matt Sicker]

Do you mean using log4j2 to log stuff from camel? If so, just add
log4j-slf4j-impl as a dependency in addition to log4j-api/log4j-core as
usual.

http://logging.apache.org/log4j/2.x/log4j-slf4j-impl/index.html

On 24 June 2016 at 07:53, N.S.KARTHIK  wrote:

> Hi
>
>  I did not get any references on the WWW  on any Simple/Sample of 'Camel
> DSL
> routes using Log4j2'.
>
>  If some body has any references/examples , plz publish the same.
>
>
> With regards
> Karthik
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-2-16-With-Log4j2-by-DSL-tp5784370.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Matt Sicker 

Camel quartz in cluster mode rewrite trigger

[Anton Ram]

Hello. I’m using camel quartz2 in cluster mode. Route starts from default 
quartz endpoint like :

Camel 2.16 With Log4j2 by DSL

[N.S.KARTHIK]

Hi

 I did not get any references on the WWW  on any Simple/Sample of 'Camel DSL
routes using Log4j2'.

 If some body has any references/examples , plz publish the same.


With regards
Karthik



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-2-16-With-Log4j2-by-DSL-tp5784370.html
Sent from the Camel - Users mailing list archive at Nabble.com.

camel xslt parsing not working with Camel 2.17.1 - Nullpointer Exception

[ganga_camel]

Hi,

I have a camel route which will tranform the incomming xml to a specified
format. I am using Camel xslt component for the same.

Everything was working fine when I was using Camel 2.16.2. When I upgrdade
to camel 2.17.1 the xml transformation stopped working with the below error,
I am using camel-saxon maven dependency...

Any help would be highly appreciated, as we have an awaited prod deployment
in a week's time.

2016-06-24 17:25:26 INFO  o.a.c.converter.jaxp.StaxConverter - Created
XMLInputFactory: com.sun.xml.internal.stream.XMLInputFactoryImpl@4398c559.
DOMSource/DOMResult may have issues with
com.sun.xml.internal.stream.XMLInputFactoryImpl@4398c559. We suggest using
Woodstox.
java.lang.NullPointerException
at
net.sf.saxon.event.ReceivingContentHandler.startPrefixMapping(ReceivingContentHandler.java:256)
at
org.apache.camel.converter.jaxp.StAX2SAXSource.parse(StAX2SAXSource.java:140)
at
org.apache.camel.converter.jaxp.StAX2SAXSource.parse(StAX2SAXSource.java:343)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:396)
at net.sf.saxon.event.Sender.send(Sender.java:143)
at net.sf.saxon.Controller.transform(Controller.java:1890)
at 
org.apache.camel.builder.xml.XsltBuilder.process(XsltBuilder.java:142)
at
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)
at
org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:128)
at
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at 
org.apache.camel.processor.SendProcessor.process(SendProcessor.java:145)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:121)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at
org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:117)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:77)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:468)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:121)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:83)
at
org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:190)
at
org.apache.camel.component.seda.SedaConsumer.sendToConsumers(SedaConsumer.java:298)
at
org.apache.camel.component.seda.SedaConsumer.doRun(SedaConsumer.java:207)
at 
org.apache.camel.component.seda.SedaConsumer.run(SedaConsumer.java:154)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Thanks,
Ganga



--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-xslt-parsing-not-working-with-Camel-2-17-1-Nullpointer-Exception-tp5784368.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Mail Body garbled when containing umlaut ue

[tippse]

reposted, because was not send to mailinglist before. 

If I send an email with an object attached to camel messeage headers, the
object and other headers are inserted into the mail body. 
I don't understand why, but I don't mind.

The problem is, if the body conains special characters like umlaut u, the
body content ist garbled. most of the body content ist missing. I tried
CamelCharsetName=UTF-8 and ISO-8859-1, but there is no difference. 

an Umlaut ue in another header or in the subject seems to be ok. 

this is a problem, since the special characters come from an
exception.message, which I have to forward in a mail. 

thanks a lot, Tippse


message body shown correctly without special character (Umlaut ue): 

header_umlaut: Umlaut ü in header
OBJECT: mandant=test, id=12345
titel: v4all-Uploader: Ein Fehler ist aufgetreten!

Umlaut ue

message body with special character (Umlaut ü, see line OJBECT!): 

header_umlaut: Umlaut ü in header
OBJECT: mandant=st, id345
titel: v4all-Uploader: Ein Fehler ist aufgetreten!

Umlaut ü

http://camel.apache.org/schema/spring; trace="true">



ISO-8859-1


nore...@somedomain.com


{{email-adress}}


${in.header.titel}


Umlaut ü in header


Umlaut ü





the object class: 
public class TestObject {

private String mandant = "test";
private String id = "12345";

@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("mandant=");
sb.append(mandant);
sb.append(", id=");
sb.append(id);
return sb.toString();
}

}





--
View this message in context: 
http://camel.465427.n5.nabble.com/Mail-Body-garbled-when-containing-umlaut-ue-tp5784365p5784366.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mail Body garbled when containing umlaut ue

[tippse]

If I send an email with an object attached to camel messeage headers, the
object and other headers are inserted into the mail body. 
I don't understand why, but I don't mind.

The problem is, if the body conains special characters like umlaut u, the
body content ist garbled. most of the body content ist missing. I tried
CamelCharsetName=UTF-8 and ISO-8859-1, but there is no difference. 

an Umlaut ue in another header or in the subject seems to be ok. 

this is a problem, since the special characters come from an
exception.message, which I have to forward in a mail. 

thanks a lot, Tippse


message body shown correctly without special character (Umlaut ue): 

header_umlaut: Umlaut ü in header
OBJECT: mandant=test, id=12345
titel: v4all-Uploader: Ein Fehler ist aufgetreten!

Umlaut ue

message body with special character (Umlaut ü, see line OJBECT!): 

header_umlaut: Umlaut ü in header
OBJECT: mandant=st, id345
titel: v4all-Uploader: Ein Fehler ist aufgetreten!

Umlaut ü

http://camel.apache.org/schema/spring; trace="true">



ISO-8859-1


nore...@somedomain.com


{{email-adress}}


${in.header.titel}


Umlaut ü in header


Umlaut ü





the object class: 
public class TestObject {

private String mandant = "test";
private String id = "12345";

@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("mandant=");
sb.append(mandant);
sb.append(", id=");
sb.append(id);
return sb.toString();
}

}



--
View this message in context: 
http://camel.465427.n5.nabble.com/Mail-Body-garbled-when-containing-umlaut-ue-tp5784365.html
Sent from the Camel - Users mailing list archive at Nabble.com.