Hi Paolo, Different bits of the code handle options with different prefixes. I just tried it out on master by modifying one of the producer tests to add the uri option, and while it did cause a change in the link attach to indicate pre-settled, the transfers themselves were not then settled, so I'd guess thats been broken at some point. There is a reason its not documented :) I've added a note to that end on the related JIRA I mentioned before.
Robbie On 23 April 2016 at 19:58, Paolo Patierno <[email protected]> wrote: > Hi Robbie, > > I already checked the source code and found this option but the parser return > an error related to unsupported option. It seems that supports only options > starting with "jms.". > > Paolo > > Sent from my Windows Phone > ________________________________ > From: Robbie Gemmell<mailto:[email protected]> > Sent: 23/04/2016 20:27 > To: [email protected]<mailto:[email protected]> > Subject: Re: QPid JMS : pre-settlement at AMQP level > > On 23 April 2016 at 15:56, Paolo Patierno <[email protected]> wrote: >> Hi all, >> >> is there a way to set the pre-settlement on the underlying AMQP protocol for >> the JMS Qpid producers ? >> >> Thanks, >> Paolo >> >> Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat >> Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor >> Twitter : @ppatierno >> Linkedin : paolopatierno >> Blog : DevExperience > > Hi Paolo, > > I *think* there may still be an undocumented/untested > "amqp.presettleProducers" uri option lurking in there that might do > what you are looking for. Pre-settled transfers is an area there is an > open JIRA to make some changes for, its likely that option could > change with it. > > Robbie > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
