Can an ActiveMQ broker be configured to accept REST services without XStream parsing the message body...
up vote
0
down vote
favorite
I would like to setup an external ActiveMQ broker that can receive messages via HTTP REST and forward them to the service provider application via openwire protocol. I do not want to have the XML messages parsed by the ActiveMQ broker, but an XStream parser appears to be built in with the ActivemQ/REST functionality?
Even when I send an XStream formatted XML message, the parser still gives an xstream.mapper.CannotResolveClassException unless class definitions for the XML elements are provided on the broker. The result is the same whether I am using the curl command or Postman. The result is also the same whether I send the message in XML or Plain Text format. I have not been able to find any way to disable this parser.
Having the ability to configure my ActiveMQ brokers to accept REST services for my applications would be amazing, but maintaining class definitions on the brokers requires tighter coupling than I would like.
So, is it possible to send non-parsed messages in this scenario?
rest activemq xstream
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
I would like to setup an external ActiveMQ broker that can receive messages via HTTP REST and forward them to the service provider application via openwire protocol. I do not want to have the XML messages parsed by the ActiveMQ broker, but an XStream parser appears to be built in with the ActivemQ/REST functionality?
Even when I send an XStream formatted XML message, the parser still gives an xstream.mapper.CannotResolveClassException unless class definitions for the XML elements are provided on the broker. The result is the same whether I am using the curl command or Postman. The result is also the same whether I send the message in XML or Plain Text format. I have not been able to find any way to disable this parser.
Having the ability to configure my ActiveMQ brokers to accept REST services for my applications would be amazing, but maintaining class definitions on the brokers requires tighter coupling than I would like.
So, is it possible to send non-parsed messages in this scenario?
rest activemq xstream
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I would like to setup an external ActiveMQ broker that can receive messages via HTTP REST and forward them to the service provider application via openwire protocol. I do not want to have the XML messages parsed by the ActiveMQ broker, but an XStream parser appears to be built in with the ActivemQ/REST functionality?
Even when I send an XStream formatted XML message, the parser still gives an xstream.mapper.CannotResolveClassException unless class definitions for the XML elements are provided on the broker. The result is the same whether I am using the curl command or Postman. The result is also the same whether I send the message in XML or Plain Text format. I have not been able to find any way to disable this parser.
Having the ability to configure my ActiveMQ brokers to accept REST services for my applications would be amazing, but maintaining class definitions on the brokers requires tighter coupling than I would like.
So, is it possible to send non-parsed messages in this scenario?
rest activemq xstream
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I would like to setup an external ActiveMQ broker that can receive messages via HTTP REST and forward them to the service provider application via openwire protocol. I do not want to have the XML messages parsed by the ActiveMQ broker, but an XStream parser appears to be built in with the ActivemQ/REST functionality?
Even when I send an XStream formatted XML message, the parser still gives an xstream.mapper.CannotResolveClassException unless class definitions for the XML elements are provided on the broker. The result is the same whether I am using the curl command or Postman. The result is also the same whether I send the message in XML or Plain Text format. I have not been able to find any way to disable this parser.
Having the ability to configure my ActiveMQ brokers to accept REST services for my applications would be amazing, but maintaining class definitions on the brokers requires tighter coupling than I would like.
So, is it possible to send non-parsed messages in this scenario?
rest activemq xstream
rest activemq xstream
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 19:38
Rachel217
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Nov 21 at 19:38
Rachel217
33
asked Nov 21 at 19:38
Rachel217
33
33
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Rachel217 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Rachel217 is a new contributor. Be nice, and check out our Code of Conduct.
Rachel217 is a new contributor. Be nice, and check out our Code of Conduct.
Rachel217 is a new contributor. Be nice, and check out our Code of Conduct.
Rachel217 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53419406%2fcan-an-activemq-broker-be-configured-to-accept-rest-services-without-xstream-par%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
