[jboss-dev] AS 5.1 and JBoss Messaging 2

[Tim Fox]

Resending

Tim Fox wrote:
> Andy Taylor wrote:
>>
>>
>> Jason T. Greene wrote:
>>> Well, as an example, we have multiple server dirs, but only one 
>>> client dir, and everything in there is part of the same classloader. 
>>> So, will an app writen against the 1.4 API work with the 2.0 API jar?
>> Applications written using pure JMS should work as the Connection 
>> Factories in JBM 2.0 have different package names.
>>> Is there any client specific code in 1.4 and 2.0 that shares the 
>>> same packages (if so that will be a conflict)?
>> I don't think there is but we can easily repackage any clashes.
>>>
>>> Is the MDB implementation in EJB3 compatible with both 1.4 and 2.0?
>> I guess this is something we need to test but as far as i understood 
>> it would just use the new JMS RA implementation that is currently 
>> being written.
>>>
>>> Do the dependency sets conflict between 1.4 and 2.0 (i.e. different 
>>> jgroups requirements etc)?
>> JBM2 no longer uses JGroups or Remoting which may have caused 
>> problems. We would make sure that JBM2 uses the appropriate versions 
>> of any other conflicts.
> We don't use anything else right now, so there is zero chance of 
> conflicts.
>
> However, we'll re-introduce JGroups dependency at a later date, but 
> we'll make sure we use the same one as AS.
>>>
>>> Is the JMX API in 2.0 BC with 1.4?
>>>
>>> Andy Taylor wrote:
>>>> Jesper has already developed JCA resource adapter for JBM 2.0, Is 
>>>> there anything apart from that we would need?
>>>>
>>>> Jason T. Greene wrote:
>>>>> Yeah thats a good point. Andy how are you guys planning on 
>>>>> handling AS components which are developed agains the JBM 1.4 API 
>>>>> being compatible with the JBM2 API. Were you going to add some 
>>>>> kind of compatibility layer?
>>>>>
>>>>> Dimitris Andreadis wrote:
>>>>>> This is an other option, however, it has other implications in 
>>>>>> how this get included. You'll have to import 2 different version 
>>>>>> of the same component (and possibly other dependencies).
>>>>>>
>>>>>> Not sure how our existing build system would support this.
>>>>>>
>>>>>> Jason T. Greene wrote:
>>>>>>> Part of the problem is that EAP is planning on including a JBM2 
>>>>>>> profile / option. IMO it would be very weird to ship something 
>>>>>>> in EAP but not in AS. Besides creating a profile, another option 
>>>>>>> we have is to include JBM2 with an install script in 
>>>>>>> docs/examples. Then someone could switch any AS profile to JBM2.
>>>>>>>
>>>>>>> Dimitris Andreadis wrote:
>>>>>>>> We have enough configurations so far, so I don't think it's a 
>>>>>>>> good idea adding any new ones until we come up with with a way 
>>>>>>>> to share most of the jars/configuration.
>>>>>>>>
>>>>>>>> In your case it's better to offer the preview as a separate 
>>>>>>>> download.
>>>>>>>>
>>>>>>>> Andy Taylor wrote:
>>>>>>>>> As part of the AS 5.1 release we will be shipping JBM 2.0 as a 
>>>>>>>>> technology preview. This will require 1 or more new profiles 
>>>>>>>>> to be created. I have created a branch (Branch_5_x_JBM2) to 
>>>>>>>>> use for now which i will merge in once JBM 2.0 is released and 
>>>>>>>>> there is something concrete and working.
>>>>>>>>>
>>>>>>>>> What new profiles we need to add is open to discussion. We'll 
>>>>>>>>> definitely need a copy of default as a start which could be 
>>>>>>>>> called messaging-2. However, from a JBM2 point of view, it 
>>>>>>>>> would be good to also demonstrate clustering which would mean 
>>>>>>>>> a copy of all, say messaging-2-all, and since JBM2 can run 
>>>>>>>>> with a minimal set of services maybe a messaging-2-minimal as 
>>>>>>>>> well.
>>>>>>>>>
>>>>>>>>> I appreciate that adding all 3 might be too many new profiles 
>>>>>>>>> to add so I'd like to hear peoples views!
>>>>>>>>>
>>>>>>>>> Andy Taylor Core Developer
>>>>>>>>> JBoss Messaging
>>>>>>>>> _______________________________________________
>>>>>>>>> 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
>>>
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
>
>


-- 
Tim Fox
Messaging Lead
JBoss - a division of Red Hat

http://jbossfox.blogspot.com/

irc.freenode.net#jbossmessaging

fox at redhat.com