jersey
  1. jersey
  2. JERSEY-1775

Extended WADL with WadlGeneratorResourceDocSupport fails when writing out the response.

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-rc1, 2.0
    • Component/s: None
    • Labels:
      None

      Description

      See ignored test in ExtendedWadlWebappTest.testWadlOptionsMethod().

      When MBW is invoked to serialize com.sun.research.ws.wadl.Application to the response stream it fails during marshalling of org.glassfish.jersey.server.wadl.internal.generators.resourcedoc.xhtml.XhtmlElementType. JAXBContext does not have classes from the package org.glassfish.jersey.server.wadl.internal.generators.resourcedoc.xhtml. These classes needs to be passed to JAXBContext from WadlGeneratorResourceDocSupport.

      The output xml is partially written (known classes are serialized) but fails in the middle of serialization. When there is no buffering of the response the test passes as 500 cannot be returned after first bytes are written to the output. The test is bad as it does not properly check returned xml on the client side. When buffering is present 500 is returned and the test fail.

      This problem is there for longer time but thanks to missing buffering and bad test it was just ignored.

      This issue is not about the buffering but to fix the extended wadl serialization.

      ADDED:
      The test
      ExtendedWadlWebappOsgiTest.testWadlOptionsMethod fails probably due to same problem (ignored now).

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Miroslav Fuksa
              Reporter:
              Miroslav Fuksa
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 3 hours Original Estimate - 3 hours
                3h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 9 hours
                9h