3 Replies Latest reply on Feb 22, 2006 9:15 AM by aloubyansky

    Planning RC2

    aloubyansky

      These are the issues I think should be solved first. I would like the project leads that depend on XB release to agree upon priorities and identify what should be done for jbossxb-rc2 (I assume rc1 is already done by Thomas...)

      - Fixing/documenting API conflicts between Branch_4_0 and HEAD
      http://jira.jboss.org/jira/browse/JBXB-45
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917551

      - JBossWS-1.0RC2 XB issues
      http://jira.jboss.org/jira/browse/JBXB-43

      - Precompiling XSD/reducing dependency on Xerces
      http://jira.jboss.org/jira/browse/JBXB-46
      http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916443#3916443

      - Moving XB to a new package reviewing public API

        • 1. Re: Planning RC2
          thomas.diesler

           

          Fixing/documenting API conflicts between Branch_4_0 and HEAD


          IMHO we should abandon/remove the sources in jboss-4.0.x and encourcage all projects to align with the binary RC1 release. The necessary changes are relatively trivial and there should be room todo so until jboss-4.0.4.

          JBossXB functional tests should live together with its sources (currently in head) and should be removed from the 4.0.x testsuite. Integration tests should stay.

          Generally, I think its a waste of resources to maintain more that one xml binding implementation other than the one we have in head.

          JBossWS-1.0RC2 XB issues


          Naturally I think this is important. However Shaun and Scott might want to provide input on the JBossWS release schedule. JBossWS-1.0 final was promissed for the end of last year and is now pessimistically rescheduled to the end of Q1/2006



          • 2. Re: Planning RC2
            aloubyansky

            Ok, so the goal of RC2 is going to be:
            - obviously, completing the task of making the XB to be a separate project (in addition, until it's done MC, for example, cannot become a separate project also)
            - and solving urgent issues for WS-RC2

            This also includes:
            - fixing/documenting API conflicts between Branch_4_0 and HEAD (JBXB-45)
            - optionally clean-up and removal of unused prototypes

            This doesn't include:
            - reducing dependency on Xerces
            - repackaging and review of public API
            - in WS, switching to the new SchemaBinding-based marshaller

            • 3. Re: Planning RC2
              aloubyansky

              RC2 has been released.

              Release Notes for JBoss XML Binding (JBossXB)
              Includes versions: JBossXB-1.0RC2

              Bug
              # http://jira.jboss.com/jira/browse/JBXB-47 marshalled string values should be normalized

              Feature Request
              # http://jira.jboss.com/jira/browse/JBXB-28 Need non-default ctor binding

              # http://jira.jboss.com/jira/browse/JBXB-40 Support for plugable serializer/deserializer

              # http://jira.jboss.com/jira/browse/JBXB-48 SchemaBinding initializer

              # http://jira.jboss.com/jira/browse/JBXB-55 Add the ability to avoid annotation parsing when you know there are none.

              Task
              # http://jira.jboss.com/jira/browse/JBXB-43 Resolve issues targeted for JBossWS-1.0RC3

              # http://jira.jboss.com/jira/browse/JBXB-45 investigate conflicts between XB versions in Branch_4_0 and HEAD

              # http://jira.jboss.com/jira/browse/JBXB-50 changing default unmarshalling rules at runtime

              # http://jira.jboss.com/jira/browse/JBXB-51 changing default marshalling rules at runtime


              The task of making the project standalone has been postponed since it requires a number of changes in the JBoss build system.