> JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry Leave this for CR1. We need to validate one issue, which likely isn't a JBC problem. Then the 3.1.0.CR1 that's been running in Branch_5_x/trunk for a couple weeks now just needs to be released as GA.

Jasone, This upgrade is Done: JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan Shelly

We still have 11 updates, and only one week is left until freeze. We also only have a week for catching regressions, so we should avoid including anything at the last minute. Therefore, let me know if any of these should *not* be moved to 5.1.0.GA (except for jboss-managed, which has to be included), and if so, when they will be included. https://jira.jboss.org/jira/browse/JBAS-6552 JBAS-6691 Upgrade JGroups to 2.6.10 Brian Stansberry JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW Pete Muir JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA Paul Ferraro JBAS-6621 Update jboss-managed to 2.1.0.GA Scott M Stark JBAS-6564 Include JBoss Negotiation 2.0.3.SP1 Darran Lofthouse JBAS-6364 Upgrade apache-beanutils to 1.8.0 David Walluck JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan

Good question. Currently we have CR versions, as opposed to the final GA, for those updates. Alexey, was this just to give time for catching regressions? Could we move to a GA in a week's time? Ales Justin wrote: > I don't see XB update on this list. > So it's probably not going in? > > But if we want to include it, > then we need the whole MC update as well. > > Jason T. Greene wrote: >> We still have 11 updates, and only one week is left until freeze. We >> also only have a week for catching regressions, so we should avoid >> including anything at the last minute. Therefore, let me know if any >> of these should *not* be moved to 5.1.0.GA (except for jboss-managed, >> which has to be included), and if so, when they will be included. >> >> https://jira.jboss.org/jira/browse/JBAS-6552 >> >> JBAS-6691 Upgrade JGroups to 2.6.10 Brian Stansberry >> JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW Pete Muir >> JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry >> JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan >> JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano >> JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA Paul Ferraro >> JBAS-6621 Update jboss-managed to 2.1.0.GA Scott M Stark >> JBAS-6564 Include JBoss Negotiation 2.0.3.SP1 Darran Lofthouse >> JBAS-6364 Upgrade apache-beanutils to 1.8.0 David Walluck >> JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic >> JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan >> >> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development

Alexey Loubyansky wrote: > Yes, the purpose of CR1 was for testing. I haven't heard of any issue > except for setting -Dxb.builder.useUnorderedSequence for the > testsuite. So, no problem with doing GA. > > I'll do maybe one more thing for the binder: if a Java type is bound > to a sequence and doesn't use @XmlType.propOrder then the binding will > fail with an exception. We've seen how missed propOrder can cause > deployment errors in 5.0.0.GA in some environments. So, really if you > bind to a sequence and don't use propOrder your project/product may > fail on a different JVM. I'll make a config option for that as well. Do you support @XmlAccessOrder(ALPHABETICAL)? This does give compliant behavior when propOrder is undefined. If so, perhaps this option should only trigger an error/warning when properOrder is undefined and XmlAccessOrder is set to UNDEFINED.

So for those of us who are mostly JAXB-ignorant - if I give propOrder={} this means that no additional order (beyond what's in the XSD, if validation is enabled) will be enforced, right? So I should be adding this to every XmlType in my MC metadata class definitions?

Why is actually order so important? I for one don't care how MC beans are described. Or any other xml for that matter. I would say just the contrary, while I remember what are some elements and attributes I will never remember the right order. And if I don't have some fancy IDE, e.g. plain notepad or joe, it's like a lottery to get it right. :-) Alexey Loubyansky wrote: > David M. Lloyd wrote: >> So for those of us who are mostly JAXB-ignorant - if I give >> propOrder={} this means that no additional order (beyond what's in >> the XSD, if validation is enabled) will be enforced, right? So I >> should be adding this to every XmlType in my MC metadata class >> definitions? > > Yes, propOrder should match the order in the XSD. And, of course, XML > should follow the same order. > > Make sure it's all consistent before the next release. > > Thanks, > Alexey > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Ales, just attend one of interoperability events involving a flavor of xml and you will realize the value of schema validation. We need to maintain proper order based on schema IMO. Alexey Loubyansky wrote: > Because you have a schema and in the schema you use sequences. If you > want, use xsd:all instead I don't mind (although it has limitations). > > XML must be valid and Java binding consistent with schemas. Or you can > take over metadata :) > > Ales Justin wrote: >> Why is actually order so important? >> >> I for one don't care how MC beans are described. >> Or any other xml for that matter. >> >> I would say just the contrary, >> while I remember what are some elements and attributes >> I will never remember the right order. >> And if I don't have some fancy IDE, e.g. plain notepad or joe, >> it's like a lottery to get it right. :-) >> >> Alexey Loubyansky wrote: >>> David M. Lloyd wrote: >>>> So for those of us who are mostly JAXB-ignorant - if I give >>>> propOrder={} this means that no additional order (beyond what's in >>>> the XSD, if validation is enabled) will be enforced, right? So I >>>> should be adding this to every XmlType in my MC metadata class >>>> definitions? >>> >>> Yes, propOrder should match the order in the XSD. And, of course, >>> XML should follow the same order. >>> >>> Make sure it's all consistent before the next release. >>> >>> Thanks, >>> Alexey _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

Because you have a schema and in the schema you use sequences. If you want, use xsd:all instead I don't mind (although it has limitations). XML must be valid and Java binding consistent with schemas. Or you can take over metadata :) Ales Justin wrote: > Why is actually order so important? > > I for one don't care how MC beans are described. > Or any other xml for that matter. > > I would say just the contrary, > while I remember what are some elements and attributes > I will never remember the right order. > And if I don't have some fancy IDE, e.g. plain notepad or joe, > it's like a lottery to get it right. :-) > > Alexey Loubyansky wrote: >> David M. Lloyd wrote: >>> So for those of us who are mostly JAXB-ignorant - if I give >>> propOrder={} this means that no additional order (beyond what's in >>> the XSD, if validation is enabled) will be enforced, right? So I >>> should be adding this to every XmlType in my MC metadata class >>> definitions? >> >> Yes, propOrder should match the order in the XSD. And, of course, XML >> should follow the same order. >> >> Make sure it's all consistent before the next release. >> >> Thanks, >> Alexey >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development >> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

So for those of us who are mostly JAXB-ignorant - if I give propOrder={} this means that no additional order (beyond what's in the XSD, if validation is enabled) will be enforced, right? So I should be adding this to every XmlType in my MC metadata class definitions?

Yes, the purpose of CR1 was for testing. I haven't heard of any issue except for setting -Dxb.builder.useUnorderedSequence for the testsuite. So, no problem with doing GA. I'll do maybe one more thing for the binder: if a Java type is bound to a sequence and doesn't use @XmlType.propOrder then the binding will fail with an exception. We've seen how missed propOrder can cause deployment errors in 5.0.0.GA in some environments. So, really if you bind to a sequence and don't use propOrder your project/product may fail on a different JVM. I'll make a config option for that as well. Jason T. Greene wrote: > Good question. Currently we have CR versions, as opposed to the final > GA, for those updates. Alexey, was this just to give time for catching > regressions? Could we move to a GA in a week's time? > > Ales Justin wrote: >> I don't see XB update on this list. >> So it's probably not going in? >> >> But if we want to include it, >> then we need the whole MC update as well. >> >> Jason T. Greene wrote: >>> We still have 11 updates, and only one week is left until freeze. We >>> also only have a week for catching regressions, so we should avoid >>> including anything at the last minute. Therefore, let me know if any >>> of these should *not* be moved to 5.1.0.GA (except for >>> jboss-managed, which has to be included), and if so, when they will >>> be included. >>> >>> https://jira.jboss.org/jira/browse/JBAS-6552 >>> >>> JBAS-6691 Upgrade JGroups to 2.6.10 Brian Stansberry >>> JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW Pete Muir >>> JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry >>> JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan >>> JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano >>> JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA Paul Ferraro >>> JBAS-6621 Update jboss-managed to 2.1.0.GA Scott M Stark >>> JBAS-6564 Include JBoss Negotiation 2.0.3.SP1 Darran Lofthouse >>> JBAS-6364 Upgrade apache-beanutils to 1.8.0 David Walluck >>> JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic >>> JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan >>> >>> >> _______________________________________________ >> jboss-development mailing list >> jboss-development(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-development > > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

So, what's the status on this. Do we need new MC GA releases or are we happy with the old one's? The old one's have not been used for a while now. Currently we use Ms, which are basically trunk snapshots. Scott, what's the current Managed version? What's the exact freeze date? Tomorrow or Monday? Alexey Loubyansky wrote: > Yes, the purpose of CR1 was for testing. I haven't heard of any issue > except for setting -Dxb.builder.useUnorderedSequence for the > testsuite. So, no problem with doing GA. > > I'll do maybe one more thing for the binder: if a Java type is bound > to a sequence and doesn't use @XmlType.propOrder then the binding will > fail with an exception. We've seen how missed propOrder can cause > deployment errors in 5.0.0.GA in some environments. So, really if you > bind to a sequence and don't use propOrder your project/product may > fail on a different JVM. I'll make a config option for that as well. > > Jason T. Greene wrote: >> Good question. Currently we have CR versions, as opposed to the final >> GA, for those updates. Alexey, was this just to give time for >> catching regressions? Could we move to a GA in a week's time? >> >> Ales Justin wrote: >>> I don't see XB update on this list. >>> So it's probably not going in? >>> >>> But if we want to include it, >>> then we need the whole MC update as well. >>> >>> Jason T. Greene wrote: >>>> We still have 11 updates, and only one week is left until freeze. >>>> We also only have a week for catching regressions, so we should >>>> avoid including anything at the last minute. Therefore, let me know >>>> if any of these should *not* be moved to 5.1.0.GA (except for >>>> jboss-managed, which has to be included), and if so, when they will >>>> be included. >>>> >>>> https://jira.jboss.org/jira/browse/JBAS-6552 >>>> >>>> JBAS-6691 Upgrade JGroups to 2.6.10 Brian Stansberry >>>> JBAS-6661 Upgrade Web Beans to 1.0.0.PREVIEW Pete Muir >>>> JBAS-6636 Upgrade JBoss Cache to 3.1.0.GA Brian Stansberry >>>> JBAS-6635 Upgrade JAXB to 2.1.9.patch Shelly McGowan >>>> JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano >>>> JBAS-6633 Upgrade jboss-ha-server to 1.2.0.GA Paul Ferraro >>>> JBAS-6621 Update jboss-managed to 2.1.0.GA Scott M Stark >>>> JBAS-6564 Include JBoss Negotiation 2.0.3.SP1 Darran Lofthouse >>>> JBAS-6364 Upgrade apache-beanutils to 1.8.0 David Walluck >>>> JBAS-6052 Upgrade jboss-profiler-jvmti to final Clebert Suconic >>>> JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan >>>> >>>> >>> _______________________________________________ >>> jboss-development mailing list >>> jboss-development(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jboss-development >> >> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

JBAS-6634 Upgrade JBossWS Native to 3.1.1.GA Alessio Soldano

> JBAS-6652 Upgrade AOP to 2.1.0.GA Kabir Khan I've released this now and updated the AS build to use it. I will be away until next Wednesday, so if you have any problems please get in touch with Flavia or Ståle.

We still have 11 updates, and only one week is left until freeze. We also only have a week for catching regressions, so we should avoid including anything at the last minute. Therefore, let me know if any of these should *not* be moved to 5.1.0.GA (except for jboss-managed, which has to be included), and if so, when they will be included. https://jira.jboss.org/jira/browse/JBAS-6552