Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0-M1
    • Component/s: javaee6, specs
    • Security Level: public (Regular issues)
    • Labels:
      None

      Description

      A new version of the jaxb specs is needed for the 2.2 level.

        Activity

        Hide
        Shawn Jiang added a comment - - edited

        There are problems in final jaxb 2.2 spec PDF:

        1, There's no TOC in the doc, it's hard to navigate the content.
        2, The content is not intact. At least, the changes log section of 2.2 spec is exactly the same with that of 2.0 spec.

        Does anyone know how to report these problems to JCP ?

        Show
        Shawn Jiang added a comment - - edited There are problems in final jaxb 2.2 spec PDF: 1, There's no TOC in the doc, it's hard to navigate the content. 2, The content is not intact. At least, the changes log section of 2.2 spec is exactly the same with that of 2.0 spec. Does anyone know how to report these problems to JCP ?
        Hide
        Rick McGuire added a comment -

        Shawn,

        If you download the jaxb-2_2-mrel2-spec.zip file from the JAXB JSR page, there is zip file in there named javadoc-diff.zip. That zip file contains very detailed information about what has changed in the API. The changes look relatively minor (one new class, two changed classes).

        Show
        Rick McGuire added a comment - Shawn, If you download the jaxb-2_2-mrel2-spec.zip file from the JAXB JSR page, there is zip file in there named javadoc-diff.zip. That zip file contains very detailed information about what has changed in the API. The changes look relatively minor (one new class, two changed classes).
        Hide
        Shawn Jiang added a comment -

        I also noticed the doc diff but I'm not very comfortable to update the spec directly just based on the java doc without reading the spec update itself.

        Show
        Shawn Jiang added a comment - I also noticed the doc diff but I'm not very comfortable to update the spec directly just based on the java doc without reading the spec update itself.
        Hide
        Rick McGuire added a comment -

        The changes are so minor, they are only documented in the javadoc. The changes.html file in the javadoc-diff zip file gives you a very detailed summary of what has changed in the API. There really appears to be just one substantial change to the API. The setDataTypeConverter() method can now throw a security exception and there is a new JAXBPermission class associated with that change. The rest of javadoc updates appear to be clarifications of how the JAXBContext.newInstance() methods are expected to work, and not necessarily changes to the APIs. None of this information is directly contained in the PDF file, so there's really are not any changes to the pdf version of the spec.

        Show
        Rick McGuire added a comment - The changes are so minor, they are only documented in the javadoc. The changes.html file in the javadoc-diff zip file gives you a very detailed summary of what has changed in the API. There really appears to be just one substantial change to the API. The setDataTypeConverter() method can now throw a security exception and there is a new JAXBPermission class associated with that change. The rest of javadoc updates appear to be clarifications of how the JAXBContext.newInstance() methods are expected to work, and not necessarily changes to the APIs. None of this information is directly contained in the PDF file, so there's really are not any changes to the pdf version of the spec.
        Hide
        Shawn Jiang added a comment -

        Got it. I've made the changes according to the javadoc diff with Rev.924100. Will see if the changes satisfy the TCK after my TCK request is approved.

        Thanks Rick for the suggestion.

        Show
        Shawn Jiang added a comment - Got it. I've made the changes according to the javadoc diff with Rev.924100. Will see if the changes satisfy the TCK after my TCK request is approved. Thanks Rick for the suggestion.
        Hide
        Shawn Jiang added a comment -

        there's only signature testing for jaxb, there won't be singature problems in the changes. Closing it.

        Show
        Shawn Jiang added a comment - there's only signature testing for jaxb, there won't be singature problems in the changes. Closing it.

          People

          • Assignee:
            Shawn Jiang
            Reporter:
            Rick McGuire
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development