I forgot to mention, that the conversion has three targets : standalone, AS5 and AS7.
AS4 is not supported. (or is it?)
+1 for AS-4. I doubt there's much of a difference between AS-4 and AS-5 as far as the configuration files are concerned.
Configurations files: including server configurations (like messaging-service.xml, remoting configs, jms destionation/factory configurations, persistent configs, bridges).
left blank should search for all files.
we should do this via some sort of mapping xml document that lists what can be converted for each version something like
<connection-factory-attribute src-name="failover-attempts" src-versions="1.1,1.2" dest-name="reconnectAttempts" dest-versions="2.2, 2.3,2.4"/>
then we can control multiple JBM,HQ versions, just an idea Howard.
Also +1 for as4
That's a good idea. Thanks Andy.
About AS4 support, I guess you guys are right. People who is running their applications in AS4 probably don't want to update their whole AS just because of updating their messaging engine.
I wrote an XML importer/exporter for moving data from one HornetQ instance to another. See https://github.com/hornetq/hornetq/tree/master/hornetq-core/src/main/java/org/hornetq/core/persistence/impl/journal. If you use the same XML format with the JBM exporter then you won't have to write the importer. That said, this is only for message data and bindings. It doesn't import/export other general configuration details.
Are you moving to this task already? I didn't see your PR on the pluggable discovery.
That's nice, it'll save quite a bit work. Thanks!
Hi Clebert, I'm going to sent out the pull request for hornetq316. I just need to pass the tests before that.
I added a sample configuration file where the user can define various migration tasks. It looks like the following:
<profile name="default" action="act1">
<target type="STANDALONE" version="2.2.14.GA" location="...">
<task type="SERVER" location="...">
<param key="jboss.home" value="..."/>