See my post on your thread. Most of that stuff is the ProfileService integration with messaging and needs to be adapted to work with HornetQ. Without it configuration changes made through the console will not work, nor will creating queues and topics from the console. Emanuel Muckenhuber and I can get into further details on the forum thread. On 01/08/2010 02:51 PM, Clebert Suconic wrote: > I'm currently working on the integration of HornetQ on AS6. > > There are a few classes on the messaging project, that I will probably > remove everything. I'm going to replace it for something more abstract > as I started a discussion here: > > http://community.jboss.org/thread/146565?tstart=0 > > > > However, I just realized that there are a few org.jboss.mq.server.jmx > classes that are just delegating to JBM 1.4. > > > I want to get rid of all that. Any objections? > > > > also... There are a couple *MO classes. (ManagedObjectDefinition) > > > I couldn't find much information about this. Is there a project for > this? Maybe I'm getting old and not being able to google properly, or > it's just a new project or something like that? > > > > clebert > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development

The original idea was to have smooth (don't need to change anything) migration of old jms config files when migrating to jboss messaging. There are lots of people out there that have -service.xml files defining their jms destinations. A quick non-scientific search of google shows a lot people are converting to the jboss messaging configs anyway. Probably because those backwards compatibility configs are not handled properly by the console: https://jira.jboss.org/jira/browse/JBAS-7051 The better solution would have been to take the opportunity to migrate to a "domain specific config": http://community.jboss.org/message/281167#281167 http://lists.jboss.org/pipermail/jboss-development/2007-November/011057.html Which would have avoided the user having to code implementation details like the class names into their config files and made them a lot clearer to read. But nothing ever came of that "ease of use" suggestion. :-(

On Fri, 2010-01-08 at 16:13 -0600, Brian Stansberry wrote: > Sorry, I focused on the *MO classes part of your message and ignored the > primary topic! > > I don't see any reason AS 6 should support -service.xml deployments that > use the old JBoss MQ classes. I recommend you give it a few days in case > there are other opinions, and if not get rid of them when you start work > on this. > > Another question though is whether we should provide a similar > compatibility layer for legacy -service.xml JBM deployments. Thoughts > anyone? > > On 01/08/2010 02:55 PM, Brian Stansberry wrote: > >> See my post on your thread. Most of that stuff is the ProfileService >> integration with messaging and needs to be adapted to work with HornetQ. >> Without it configuration changes made through the console will not work, >> nor will creating queues and topics from the console. >> >> Emanuel Muckenhuber and I can get into further details on the forum thread. >> >> On 01/08/2010 02:51 PM, Clebert Suconic wrote: >> >>> I'm currently working on the integration of HornetQ on AS6. >>> >>> There are a few classes on the messaging project, that I will probably >>> remove everything. I'm going to replace it for something more abstract >>> as I started a discussion here: >>> >>> http://community.jboss.org/thread/146565?tstart=0 >>> >>> >>> >>> However, I just realized that there are a few org.jboss.mq.server.jmx >>> classes that are just delegating to JBM 1.4. >>> >>> >>> I want to get rid of all that. Any objections? >>> >>> >>> >>> also... There are a couple *MO classes. (ManagedObjectDefinition) >>> >>> >>> I couldn't find much information about this. Is there a project for >>> this? Maybe I'm getting old and not being able to google properly, or >>> it's just a new project or something like that? >>> >>> >>> >>> clebert >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >>> >> >> > >