Content_type needs to be configurable about rabbitmq-jms-client HOT 8 CLOSED

@mcgiri Here's a workaround: #19 (comment)

from rabbitmq-jms-client.

There's no standard content type header in JMS. The best we can do is to provide an interface to customize the AMQP.BasicProperties.Builder:

public interface AmqpPropertiesCustomizer {
  AMQP.BasicProperties.Builder customize(AMQP.BasicProperties.Builder builder, Message jmsMessage);
}

Your implementation could be the following:

public class ContentTypeAmqpPropertiesCustomizer implements AmqpPropertiesCustomizer {

  public AMQP.BasicProperties.Builder customize(AMQP.BasicProperties.Builder builder, Message jmsMessage) {
    String contentType = jmsMessage.getStringProperty("content_type");
    if (contentType != null) {
      builder.contentType(contentType);
    }
    return builder;
  }

}

The customizer instance would be set at the RMQConnectionFactory level. @mcgiri Would that work for you?

from rabbitmq-jms-client.

@acogoluegnes -- Apologies, i am going to take couple of days to get back since I am calling it from an app which uses native JMS methods, and I need to look at options to use the interface. I guess it should work but let me come back.

from rabbitmq-jms-client.

@acogoluegnes -- Even with the interface, the content_type would still be set to "application/octet-stream" right? Is there a way to not set it at all?

from rabbitmq-jms-client.

As far as I can tell, that is the case. It's certainly possible to have that field blank in the underlying Java client, though.

from rabbitmq-jms-client.

@mcgiri The customizer would be applied after, so it could override the previous value of content_type.

from rabbitmq-jms-client.

@acogoluegnes Can you please include the interface? I should be able to use it. Sorry for the delay again. Thanks!

from rabbitmq-jms-client.

@mcgiri 1.9.0.RC1 has shipped with this feature, you can give it a try.

from rabbitmq-jms-client.