Re: Configuring Message Transformatin on ConnectionFactory (ACTIVEMQ)

[tippse]

sorry, I didn't realise, that the linked article is not up-to-date. 

the class org.apache.activemq.util.oxm.XStreamMessageTransformer seems to be
deprecated after activemq 5.7.0. 
I couldn't find proper replacement. any suggestions here are welcome, but
this ist obviously no camel problem. 

I got it working though, by using my own custom transformer, extending
org.apache.activemq.MessageTransformerSupport






 




--
View this message in context: 
http://camel.465427.n5.nabble.com/Configuring-Message-Transformatin-on-ConnectionFactory-ACTIVEMQ-tp5787239p5787242.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Configuring Message Transformatin on ConnectionFactory (ACTIVEMQ)

[tippse]

as explained here: ( http://activemq.apache.org/message-transformation.html
  ) a Message
Transformer can be configured on the connection factory. That way all
objectmessages are transformed automatically. 

Is there a way to use this in camel? 

I know, that a transformation can be configured via dataformat. but as far
as I know, this must be on configured in every single route using activmq. I
would like to avoid this. 

thanks a log, 
febi





--
View this message in context: 
http://camel.465427.n5.nabble.com/Configuring-Message-Transformatin-on-ConnectionFactory-ACTIVEMQ-tp5787239.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.

MS listener (Activemq) is not forwarding to onException-Clause

[tippse]

I wonder why the RuntimeCamelException ist not caught in the global
onException Clause. 
But Exceptions in the myListener-Bean are forwarded as expected.

Exception: 
Execution of JMS message listener failed. Caused by:
[org.apache.camel.RuntimeCamelException - Failed to extract body due to:
javax.jms.JMSException: Failed to build body from content. Serializable
class not available to broker. Reason: java.lang.ClassNotFoundException:
Forbidden class java.util.LinkedHashMap! This class is not trusted to be
serialized as ObjectMessage payload.








java.lang.Throwable
 


The Exceptions happens, because the class is not known to the broker. 
In such cases of missing configuration there should be an email sent, which
is configured in the onException.

camel-version 2.17.1
activemq-version5.13.3

thanks, tippse





--
View this message in context: 
http://camel.465427.n5.nabble.com/MS-listener-Activemq-is-not-forwarding-to-onException-Clause-tp5783855.html
Sent from the Camel - Users mailing list archive at Nabble.com.