April 2007 - jboss-development - Jboss List Archives

Re: [jboss-dev] JBoss Messaging - to scope or not to scope

by Tim Fox

Ram Venkataraman wrote: > I talked to Ovididu about a month or so ago when Messaging went GA and > spoke about integration JBM into 4.x and I clearly remember asking > about remoting. He did not raise any red flags, in fact we spoke of it > being compatible. > > I will raise this in the next platform meeting. We are ready to go to > beta next week. We definitely cannot change anything at this time. I am > adding Patrick to this thread to see if this something that we can > change during the beta period without much impact. > > Do we know what impact an upgrade to Remoting 2.2 have on the other > parts of the appserver ? No, but the impact of _not_ upgrading AS4.2 with Remoting 2.2 is clearer: 1) Messaging would have been be deployed scoped for the whole of the 4.2 series. This means no "real" integration in the 4.2 series for messaging. 2) ESB would have been be deployed scoped for the whole of the 4.2 series when used in app server (please correct me if I am wrong Kevin/Mark). Again, this means no "real" integration in the AS for the 4.2 series assuming it is using JBM as it's default transport. 3) Remoting would be stuck at 2.0 for the whole series (or longer?). Since 2.2 is not compatible (acccording to Ron). Scoping ==> useability nightmare + barrier to adoption (AFAIK we should be able to drop remoting 2.2.0 into 4.2 without problems - but of course this is untested). Also bear in mind that a heck of a lot of bugs have been fixed between remoting 2.0 and 2.2. So if you ship with 2.0 you're shipping with those bugs too. > > Ram > >

18 years, 12 months

1
0
0 / 0

microcontainer-head-testsuite Build Failed

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

ejb3-4.2-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jboss-aop-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jboss-4.0-testsuite-win-sun-1.4 Build Failed

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jbossretro-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jbpm.3 Build Failed

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

Re: [jboss-dev] JBoss Messaging - to scope or not to scope

by Tim Fox

Ron Sigal wrote: > Remoting 2..0.0.GA was released around 8/29/06, so quite a bit has been > done since then. Unfortunately, 2.2.0.GA is not completely compatible > with 2.0.0.GA at the wire level. We won't let that happen in the future. > > -Ron > I thought remoting supported wire format version from some time ago? I.e. a 2.0 client should work with a 2.2 server? Are you sure this is not the case? This was a requirement from messaging a long way back. I remember getting Tom to add it. Remoting adds a version byte on each request, doesn't it? Ron - how hard would it be to backport the changes between 2.0.0 and 2.2.0 into 2.0.1 and keeping wire format and compile time API compatibility with 2.0.0? (This would basically mean renaming 2.2.0 to 2.0.1 and ensuring compatibility with 2.0.0 ??) This would be crucial for deploying messaging (and esb) unscoped in the 4.2.x series.

18 years, 12 months

1
0
0 / 0

jboss-seam-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development April 2007