You are viewing a plain text version of this content. The canonical link for it is here.
Posted to gitbox@activemq.apache.org by GitBox <gi...@apache.org> on 2019/04/25 03:51:18 UTC

[GitHub] [activemq-artemis] ldebello edited a comment on issue #2634: ARTEMIS-2316 AMQPMessage missing ApplicationProperties from custom transformer

ldebello edited a comment on issue #2634: ARTEMIS-2316 AMQPMessage missing ApplicationProperties from custom transformer
URL: https://github.com/apache/activemq-artemis/pull/2634#issuecomment-486510092
 
 
   I partially agree with both, because I think the behaviour should be consistent at least during a patch release, although there was a error, some kind of "bug feature" because the fix which generate the fix was about performance, I think it was a collateral effect and not a real fix for that specific use case.
   Having said that if the idea is to force the use to call reencode if they modify the message, I think that should be changed from 2.8.0 onwards but only reverting this commit does not solve all the cases, because if you send a message, inject properties, does not call reencode and consume the message from the same broker the properties are there, which is weird, this issue arise when the bridge has to serialize the message and I suppose if you have too many message and pagination start working maybe the "issue" is present as well.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services