Skip to content

Commit 9ef3e6f

Browse files
authored
Update README.md
1 parent e0718a5 commit 9ef3e6f

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

README.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -128,9 +128,6 @@ Everything is the same as above, except you call `sendMessageToQueue` method and
128128
129129
Messages are always read from the default queue (specified at creation of the `api` object). Message body can be received as text or as a stream.
130130
131-
132-
`props` should have 15 elements in the case message mody would be returned as a stream, and 16 if it would be returned as a string. In that case 16th element would be message body.
133-
134131
#### Reading message as a stream
135132
136133
First you need to prepare `props` to pass by reference into Java and then call `readMessageStream`:
@@ -149,18 +146,19 @@ Set msg = api.readMessageStream(.props)
149146
150147
#### Reading message as a string
151148
152-
153149
```
154150
#Dim api As isc.rabbitmq.API
155151
#Dim msg As %GlobalBinaryStream
156152
#Dim props As %ListOfDataTypes
157153
Set props = api.readMessageString()
158154
```
159155
160-
`props` would be filled with message metainformation, not that you don't need to init it on InterSystems side before calling RabbitMQ.
156+
`props` would be filled with message metainformation, note that you don't need to initialize it on the InterSystems side before calling RabbitMQ.
161157
162158
#### Props
163159
160+
Elements appearing in `props`. All of them besides first and second are optional. Conversion from list into `RabbitMQ.Message` is available in the `ListToMessage` method of `RabbitMQ.InboundAdapter` class.
161+
164162
| Position | Name | Description |
165163
|----------|-----------------|---------------------------------------------------------------|
166164
| 1 | Message Length | Length of a current message |

0 commit comments

Comments
 (0)