On Thu, 21 Nov 2019 at 19:03, Kristofor Horst <[email protected]> wrote:
> Hello, > > Is there a generally accepted best practice/tool that can easily migrate an > xml configuration compatible with qpid 0.20 to the json format required of > 6.1.4? > Wow - that's an old version :) - looking back 0.20 was released in January 2013, almost 7 years ago! > > I've manually entered the information but it is very time consuming if I > have to do so in the future. Also, it is prone to human error in > transcription in this way so I would prefer a tool if one is available. > > I think the suggestion back in the original timeframe that the changes were made was to load the XML config into a 0.22 (or maybe later - maybe someone with a better memory than me can recall) broker and then extract the configuration as JSON via the HTTP management API. There is this mail thread http://qpid.2158936.n2.nabble.com/Qpid-0-22-how-to-pass-in-xml-config-file-tp7595486.html which talks about how to use virtualhosts.xml on a 0.22 broker. I couldn't immediately find anything on extracting using HTTP. > I was not able to find any posting for this topic in the archive, so my > inclination is that you must do it manually. > > Furthermore, if I am change controlling my configuration files, can I be > guaranteed that the order of the file will remain unchanged when a new > queue > or exchange is added? > As far as I remember, the broker will always store configuration in a stable order - however if the config is edited outside of the broker, then that order will not be maintained - rather the config will be written in the order the broker will always sort it. > > The order remaining unchanged facilitates doing a file compare to check my > inclusions. > > Thanks, > Kristofor > > > Hope this helps in some way. -- Rob > > -- > Sent from: > http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
