the encoding won't change that at all. The XML is using a producer to send to import to the broker.. not dealing directly with the journal.. so it shouldn't affect it.
On Thu, Feb 9, 2017 at 3:24 PM, Christopher Shannon <[email protected]> wrote: > Agreed that stuff like a new plugin API shouldn't break anything. Things > like that should hopefully just be enhancements and old public APIs would > still work in Artemis. > > Also, related to our other thread on importing data, it might be nice to > have a first version of the KahaDB exporter to Artemis XML done in time for > version 2.0.0. Not sure how the refactoring of encoding of messages will > effect that. > > What I have so far is here: > https://github.com/cshannon/activemq-cli-tools/tree/queueExportTest > > It's still very rough and isn't done yet but so far I have a unit test test > that does the following: > > -writes 10 text messages to a Queue in a KahaDB store > -exports the 10 messages to XML > -creates a new Artemis broker and imports the XML into the Artemis store > -then creates a new JMS consumer and consumes all 10 messages from the > Artemis broker > > > On Thu, Feb 9, 2017 at 12:57 PM, Clebert Suconic <[email protected]> > wrote: > >> I don't think it would break the API, it would be an addition.. not >> breaking anything.. >> >> >> I would still support the current APIs we have now... >> >> >> however the refactoring I'm doing will: >> >> >> - Break how Interceptors work... >> - Make the possibility of interacting of message bodies and properties >> easier (It should make it actually fairly easy to implement anything >> around Message types) >> - Break the journal >> >> >> Once the pure encoding is implemented, adding an API around >> intercepting messages at the broker level should be easier. I don't >> think that should break anything. >> >> >> I'm not talking about scheduling the release here (if it should or not >> go on the 2.0).. just what I think in technical terms regarding >> breaking the APIs. >> >> On Thu, Feb 9, 2017 at 12:03 PM, Matt Pavlovich <[email protected]> >> wrote: >> > Martyn- >> > >> > I think an important API breakage issue is plugin support. >> > >> > -Matt >> > >> > >> > >> > On 2/9/17 6:18 AM, Martyn Taylor wrote: >> >> >> >> All, >> >> >> >> As discussed in a previous thread [1] Artemis master has had a major >> bump >> >> (due to major model refactor). >> >> >> >> The great news is that the new model is more flexible and lends itself >> >> well >> >> to 5.x features like Virtual Topics as well as being consistent across >> all >> >> protocols. The not so good news is that this work required API >> breakages, >> >> hence the major version bump.). This refactor work (mostly around the >> >> addressing scheme [2]) is now completed. >> >> >> >> The code base is now in a stable state, and as such, I'd like to start >> >> thinking about doing a release off of master as an Apache Artemis 2.0.0 >> to >> >> get the new changes into the hands of users. >> >> >> >> I'd like to open discussion around this topic, does anyone have any >> >> suggestions, or can think of anything that is needed before we go ahead >> >> with a major release? This is the perfect time to do anything that could >> >> break APIs, drop deprecated methods support, break data format etc... >> >> >> >> Cheers >> >> Martyn >> >> >> >> [1] >> >> >> >> http://activemq.2283324.n4.nabble.com/DISCUSS-Artemis- >> addressing-improvements-JMS-component-removal-and- >> potential-2-0-0-td4719262.html >> >> >> >> [2] https://issues.apache.org/jira/browse/ARTEMIS-780 >> >> >> > >> >> >> >> -- >> Clebert Suconic >> -- Clebert Suconic
