ISSUE WITH KAMELET azure-servicebus-source output is message length instead of message

[bjethwan]

I had below KameletBinding working with Timer source but with Azure ServiceBus.
I was getting a type conversion error
Caused by: org.apache.camel.NoTypeConversionAvailableException: No type converter available to convert from type: com.azure.core.util.BinaryData to the required type: java.io.InputStream

Hence, I added a JSON Serializer in between

apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
  name: aws-s3-streaming-upload-sink-binding
spec:
  source:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: azure-servicebus-source
    properties:
      connectionString: Endpoint=<<>>/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=<<>>
      topicOrQueueName: <<>>
      serviceBusReceiveMode: RECEIVE_AND_DELETE
  steps:
  - ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: json-serialize-action
  sink:
    ref:
      kind: Kamelet
      apiVersion: camel.apache.org/v1alpha1
      name: aws-s3-streaming-upload-sink
    properties:
      bucketNameOrArn: arn:aws:s3:::<<>>
      keyName: timer-source
      region: ap-south-1
      accessKey: <<>>
      secretKey: <<>>
      batchMessageNumber: 5

Now the PROBLEM is that instead of capturing data it's capturing length of the message
{"length":54}{"length":54}{"length":54}{"length":54}{"length":54}

How to fix this?
Do I need to configure the azure-servicebus-source Kamelet to make it output String/JSON? Is it reasonable to configure the Kamelet or should I copy and configure that one?

[oscerd]

What you get in the body are binary data: https://docs.microsoft.com/en-us/java/api/com.azure.messaging.servicebus.servicebusreceivedmessage.getbody?view=azure-java-stable#com-azure-messaging-servicebus-servicebusreceivedmessage-getbody()

So the behavior is correct if you try to serialize it through json-serialize action

[oscerd]

Feel free to re-open or ask again.

[bjethwan]

@oscerd Hi Andrea
But I do have the json-serialize-action defined between the source and sink. Is it not the correct way? Please check the yaml given in my original post