Dhairya-007 opened a new pull request, #29541: URL: https://github.com/apache/camel/pull/29541
Three message headers are documented with the text of the header declared next to them, so the catalog and the generated docs tables describe two headers identically: | Component | Header | Documented as | Set by the code as | | --- | --- | --- | --- | | aws2-ddb | `CamelAwsDdbItems` (Query, Scan) | *The list of attributes returned by the operation.* (= `CamelAwsDdbAttributes`) | `result.items()` in `QueryCommand`/`ScanCommand`: the list of items | | mongodb | `CamelMongoDbResultPageSize` | *Number of objects matching the query. This does not take limit/skip into consideration.* (= `CamelMongoDbResultTotalSize`) | `result.size()` after `skip`/`limit` were applied in `MongoDbProducer`, so it is exactly the count that *does* take limit/skip into consideration | | smpp, smpps | `CamelSmppAlphabet` | *The data coding according to the SMPP 3.4 specification, section 5.2.19. Use the URI option `alphabet` settings above.* (= `CamelSmppDataCoding`) | `SmppSmCommand` reads it as the alphabet; the component docs already say "The alphabet corresponds to bits 0–3 of the data coding field" | `CamelSmppDataCoding` keeps its text but now points at the `dataCoding` URI option rather than `alphabet`, which is the option for the other header. New descriptions: - `CamelAwsDdbItems`: The list of items returned by the operation. - `CamelMongoDbResultPageSize`: Number of objects returned by the operation, after limit/skip have been applied. - `CamelSmppAlphabet`: *For SubmitSm, SubmitMulti and ReplaceSm* The alphabet according to the SMPP 3.4 specification, section 5.2.19, which is bits 0-3 of the data coding. Use the URI option `alphabet` settings above. - `CamelSmppDataCoding`: … Use the URI option `dataCoding` settings above. The `@Metadata` on the constants is changed and the component JSON files plus their `camel-catalog` copies (byte-identical) are updated by hand to what the generator would emit. Doc-only change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
