[JBoss-dev] Re: JBossMQ in JBoss5

[Tim Fox]

I can understand that we need to continue to _support_ JBoss MQ with 
JBoss 5, but I don't really understand why we need to _bundle_ it with 
the distribution.

I think bundling would be sending the wrong message - (why are we 
pushing two products?), and also may confuse users, especially the ones 
new to JBoss who may not know the difference between MQ and messaging, 
and may end up install the wrong one.

For customers who really don't want to / can't move to JBoss Messaging 
when they move to JB5 , then we can provide a download and a script they 
can run, as Sacha has suggested. I think this makes more sense.


Sacha Labourey wrote:
> can we instead make JBoss MQ be an optional download/drop-in for JBoss 5.0?
> 
> Ovidiu Feodorov wrote:
>> OK, so the decision to bundle JBossMQ with JBoss 5 is taken and etched 
>> in stone?
>>
>> Andrig T Miller wrote:
>>> Okay.  Makes perfect sense.
>>>
>>> We should start a discussion on what things customers are doing with 
>>> JBossMQ that are barriers to moving to JBoss Messaging.  This is very 
>>> important for the messaging project to understand.
>>>
>>> Also, we will still need to make sure that any feature enhancements 
>>> to JBossMQ are also put into JBoss Messaging.
>>>
>>> Thanks.
>>>
>>> Andy
>>>
>>> On Mon, 2006-09-18 at 16:59 +0200, Adrian Brock wrote:
>>>> On Mon, 2006-09-18 at 14:35 +0000, Andrig T Miller wrote:
>>>> > Why is a conversion not an option for some customers? 
>>>> Because some customers add bits to JBossMQ,
>>>> e.g. writing their own persitence manager or interceptor.
>>>> Admittedly it is not that common, but it happens.
>>>>
>>>> More common is use of the JMX interface/names for 
>>>> management/monitoring.
>>>>
>>>> e.g. a common usage is creating a queue/topic "on the fly"
>>>> (not a temporary queue).
>>>>
>>>> JBoss Messaging and MQ are not compatible at this
>>>> level so it requires an investment in retooling
>>>> where it is used.
>>>>
>>>> The important part is that they have time to do
>>>> this with a sufficient notification, without
>>>> being left behind.
>>>>
>>>> Besides, it shows an investment in long term support.
>>>> Telling people "we don't support that anymore,
>>>> look at this shiny new toy instead" isn't always
>>>> what they want to hear. :-)
>>>>     
>>> Andrig (Andy) Miller
>>> VP, Engineering
>>> JBoss, a division of Red Hat
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>   
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>   
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
>